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.

In systems where callbacks or socket streams from the server to the client are
active and the server is protecting itself, I've always had the server make the
best effort to forward data to the client, using a highwater mark to start
dropping events that are getting consumed.  I then have the client, at a much
longer interval than it takes to perform the transfer of "the current state",
just retrieve a fresh view of the world.  This allows all kinds of connectivity
to provide a "current view" that is a timely as the clients connection allows.

Gregg Wonderly

===========================================================================
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