Thanks Niclas for this quick answer.

I have made my own S3 entity store (based on the non working one) and I am
indeed speaking about the MemoryEntityStore's mixins of the 0.8 SPI.

I'll wait for the event based one to appear to update my own S3 ES.

BTW, my S3 ES is a bit more complicated since it uses a cache and a
background queue of events to apply to S3 (which is too slow...).

So if you like to, I can maintain the next version of the S3 ES...

Cheers,

phil


Niclas Hedhman wrote:
> 
> Phil,
> 
> We have already decided that the event based implementation and ES SPI is
> no
> good. We are rushing to revert back to a simpler sytem, much closer to the
> original state based one.
> 
> The S3 impl that sits in sandbox is still 'using' the old SPI (hence
> doesn't
> work), but I'm sure we will get operating shortly after the overhaul.
> 
> Cheers
> Niclas
> 
> On Jul 28, 2009 10:04 PM, "philippe van dyck" <[email protected]> wrote:
> 
> Hi all,
> 
> in MapEntityStoreMixin there is a getEntityState method made of 2 parts :
> 1)
> bring the state up to date / 2) get the actual state.
> 
> In the first loop (while), we gather events and in the second (for) we
> apply
> them.
> 
> Since they are stored in the entitystore... when do we delete those events
> after they are applied ?
> 
> I am using my S3 entity store and I end up with tons of those... I would
> really like to clean this up ;-)
> 
> Any idea about a simple way to get rid of it ?
> 
> Phil
> 
> 
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
> 
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
> 
> 

-- 
View this message in context: 
http://www.nabble.com/UoW-event-lifecycle-tp24700210p24703260.html
Sent from the Qi4j-dev mailing list archive at Nabble.com.


_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to