Re: LookupDiscovery MulticastTimeToLive
Mark Brouwer <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Rikard Elofsson wrote: > It's a jungle out there... Anyway, I'm currently going with the > suggested method of using groups to manage different developers services > for now. When deployed "for real" I still really need to set multicast > TTL. Is it "enough" to set net.jini.discovery.ttl or should I also set > discoveryConstraints? Supspenders and belt? Rikard, can you explain why you have to set the TTL to 0 for production? If e.g. the reason is that you are not allowed to use multicast then it is probably better to disable multicast altogether and use unicast lookup, especially in the light of problems related to a TTL of 0. Although you probably can find reasons to want to have the dynamics of multicast discovery on the localhost, for me this is nearing the qualification of "uninteresting" (borrowing the words of somebody else :-). With regard to net.jini.discovery.ttl I couldn't find the system property in the docs or src of the 2.1 release so I doubt that one is still there, it seems you have to specify constraints. -- Mark -------------------------------------------------------------------------- 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]