The Artima Developer Community
Sponsored Link

Legacy Jini Forum
The Jini Lookup Service



This page contains an archived post to the Jini Forum made prior to February 25, 2002. If you wish to participate in discussions, please visit the new Artima Forums.



Posted by Bill Venners on February 28, 2000 at 12:25 PM

> Enjoyed the article and wanted to send you a note to let you know I like the proposed changes.
> One downside is that the small device will need to do a bit more hunting and pecking to find
> the necessary service. The cost will be in time and network hits but at the gain of not having
> to load so many unnecessary classes.
Well, the small device will have a choice whether to hunt and
peck or root through big chunks. If it has enough resources for
the big chunks, it could use that. If it finds it doesn't have
enough resources, it can switch to a hunt and peck strategy.

> Also noticed a few typos in the article which might detract from the help it provides.
> In both instances, you define the return from lookup as an array of ServiceMatches[].
> For the two-parameter form this should just be ServiceMatches and the one-parameter form
> should just be Object. I think this also propagated into your two proposed methods.
> The method getServiceIDs should return ServiceIDMatches rather than ServiceIDMatches[]
> and getEntries should return EntryMatches rather than EntryMatches[].

Thanks for the info about the typos. I'll send this to JavaWorld.



Sponsored Links

Copyright © 1996-2009 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us