Re: Outrigger and blitz -- lingering take?

Logan, Patrick wrote:
> "From the early days of GigaSpaces the take operation checks if the
> client really exists before actually removing the entry from the
> space. "
>
> I wondered whether a space implementation might track whether a taker
> was "ready" and pass by those that aren't. Yet as an application
> developer I still have to account for other ways an entry could get
> lost, so it still comes down to using a tx when it really matters.
>

Yes, ultimately I think using a tx is the best way to cover all the
common cases.  Note Blitz does provide a "loopback transaction manager"
that is it exposes it's internal transaction management as a Jini Txn
Manager lookalike so you can have all the benefits of a tx without the
need for Mahalo and with a reduced number of network roundtrips.

Note that the loopback manager is specific to each Blitz instance so it
can't co-ordinate a transaction across multiple Blitz instances.

> Thanks -Patrick

Cheers,

Dan.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html