Re: LookupCache, ServiceDiscoveryListener and discard guarantees
Bob Scheifler <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
> The specification for ServiceDiscoveryListener (at the end of > http://java.sun.com/products/jini/2.1/doc/specs/html/servicediscutil-spec.html#1004669) > makes some concurrency guarantees > > But when checking the ServiceDiscoveryManager for your answer I think > (it is rather complicated code) the current implementation doesn't seem > to implement that guarantee. Good catch, that requirement does seem to have been lost along the way. > There is some sequential processing > enforcements but that is related to the ServiceID from which the events > originate but given the various places from where these invocations can > take place but to me it doesn't look like there is proper > synchronization as the ServiceDiscoveryListener seems to require. With respect to the original question about order of Removed/Added on a listener, the ServiceID task ordering should have helped, but at least one Added call can occur in a task that is not ordered by ServiceID. - Bob -------------------------------------------------------------------------- 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]