On Jan 2, 2013, at 635AM, Dan Creswell wrote: >>>> These methods could easily return jini://host:port for standard Jini >>>> unicast >>>> discovery, this allows a lot more freedom for future expansion of >>>> discovery >>>> methods, for very little effort. >>>> >>>> >>> >>> >>> How would you see these being used in a real system? Would I want >>> these URL's on the Registrar? See, to get them, I need to have got >>> hold of the Registrar in the first place. Dunno, this feels like >>> something that needs to be on an Admin interface somewhere. >>> >> >> Got time for an example? >> > > You offering or asking? Can't tell. > > The thing about getting these locators from the registrar itself is > that you have to have located the registrar in some other way > previously (e.g. via multicast). > > Question then would be, who uses unicast lookup locators and why?
I've used locators most always when deploying into production because multicast is typically turned off. We've done other crafty things like writing a tunneling service (Lincoln) that forwards Jini Lookup Service Announcement requests and Jini Request announcements from one network to another, and also providing a different approach by using a gateway service on a well pre-defined addr:port that dispenses LookupLocators based on the lookup discovery groups being sought after. I've found locators to be key. I dont use them for firewalls, just for deployments where multicast is turned off. HTH Dennis
