Any one have any thoughts about DNS-SD for River's Services over the
internet?
I'm wondering if DNS-SD should only be used for discovery of Registrars
or whether it should include the ability to locate all Jini Services?
I'm leaning towards discovery of Registrars only.
Perhaps an Internet facing Registrar might only allow for Services to be
looked up, or to notify new registrations, external services shouldn't
be able to register with any particular domain Registrar they like?
Then when you think about mobile devices, with dynamic ip addresses,
you'd want them to be able to register with some static ip assigned
Registrar, in order to be locatable.
Then when you think about devices that cannot utilise a service, but can
provide one, then how should they advertise the presence of their
service? They need to provide a downloadable implementation of a
Service Registrar, fully contained within a smart proxy.
So really there is this possibility that we might be dealing with
immutable Registrar's, where notify might be used to notify a client
that a services location had changed, but register is ignored. This
does however present a problem to services trying to register with an
immutable Registrar, Services will continue to try to register, there is
no behaviour specified to reject registration, other than to throw a
RemoteException, followed by another attempt to register.
It seems an Internet Registrar would need to share a common super
interface with Service Registrar, but also have the ability to reject a
registration? Perhaps a ServiceRegistrar compatibility layer might
redirect a registration destined for an internet Registrar to a local
domain Registrar with an identical group name?
Any ideas / thoughts?
Cheers,
Peter.
