Re: Depending on policy [was Re: Implementation of take (multiple) in Jini starter kit]

John McClain - Sun Microsystems, Inc. wrote:
>> Having said that, it [take multiple's option to remove fewer entries
>> than asked for] does cause a problem for clients that know there
>> are 10 entries in the space and they would like to be able to get them
>> all out in one atomic call w/o bothering with a transaction.
>
> This brings up a general question that I would be interested to hear
> people's opinions on.  The spec can't say "10 is safe, but 11
> might not be (or isn't)" but individual implementation often will.
> Indeed with Outrigger in its default configuration it is safe to pass 10
> for maxEntries and if there are 10 entries in the space (and no
> contention, etc., etc.) one take call will atomically remove all 10
> entries (or remove none) w/o having to resort to loops and transactions.
>
> The question is how do people feel about depending on such behavior? Do
> you feel better about if you look at the other implementations and find
> they support similar policies (possibly after configuration)?
>
> Other places this comes up in the spaces world is support for
> arbitrarily long leases (do I assume my request for a 2 day lease will
> be granted, or do I need to be prepared to renew the lease) and how the
> space picks what entry(ies) to return from a query when there is more
> than one possibility (do I code assuming the space will be mostly FIFO?)

Could you perhaps rephrase the question?

Thanks,
James Grahn

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