Niclas Hedhman skrev: > On Tue, Sep 9, 2008 at 6:56 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > > >> The Space semantics (if I have understood them) are pretty cool in >> that the entry has to be removed from the space, modified and put back >> into the space. If you don't own the entry, you can not modify it >> > > Perhaps this wasn't clear enough; It is not possible to modify the > entry while it is in the space, and for our Entity view of the world, > it means we have a bunch of choices on how the update of an entity is > to happen. > >
Niclas, are you referrring to the JavaSpaces spec only now? GigaSpaces has a lot more features when it comes to transactional behaviour, and there is also an update method. So from the clients point of view, it is possible to do an update as opposed to a take/write. I suppose you already know about this, so the question then becomes: When you talk about spaces, do you assume only Sun / Apache River ) JavaSpaces? /Niklas > Right now, I am a bit unclear on how to do this in reality, if > multiple EnityStores are involved running on separate hosts. > > > Cheers > Niclas > > _______________________________________________ > 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
