Re: LookupCache, ServiceDiscoveryListener and discard guarantees
Gregg Wonderly <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Mark Brouwer wrote: > Given all the stuff LookupCache takes care off and the amount of time > that goes in building "state maintaining utilities while getting input > from a thousand places". I really try to understand why one wants to > build something similar although different, has it something to do with > the reliance on remote events or your particular lookup service API? The primary impetus is, in fact, remote events and the fact that they might not be delivered. Thus, my code, because it periodically polls, will eventually discover missing services. It doesn't audit for service deregistrations though, so I don't drop services explicitly. Rather the "cache" reflects what is currently visible. My work on the reef.dev.java.net stuff did not involve the caching issue. Gregg Wonderly -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]