Re: Implementation of take (multiple) in Jini starter kit

John McClain - Sun Microsystems, Inc. wrote:
> Having said all that, for me the main motivation for the phrase "an
> implementation may chose to take fewer entries from the space than the
> maximum available or the maximum allowed by maxEntries" was so the space
> could protect itself from have to load all the entries into memory so it
> could ship them back to the client, given that Outrigger keeps all of it
> entries in memory its quite possible that Interger.MAX_VALUE (we use an
> array internally so takeMultipleLimit has to be an int) would be a safe
> value for takeMultipleLimit and assume that the client would use
> maxEntries to make sure it wasn't trying to take "too many".
>
> Hope this helps. Was there a question behind the question?

There was no question behind the question; thank you for your extensive
answer.

We'll most likely change the setting to Integer.MAX_VALUE since our
processes usually have ample memory, and that will adhere to our
expected behavior.

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