Sim IJskes - QCG wrote:
On 11/08/2010 12:54 AM, Peter Firmstone wrote:
TXT keys:
txtvers=<8 bit byte version number of the DNS-SD TXT record format>
dpv=<8bit byte discovery protocol version number>
sid=<128bit hash code service ID>
grp=<comma separated list of group names to which the service belongs>
DNS is mostly managed by people other than programmers. DNS managing
departments are not eager to provide DDNS access to their zone.
So, should we limit the SRV records info to only point at an IP +
port, similar to the jini: url used in LookupLocator?
You can have the department responsible for the zone maint, create a
SRV record once, and you can be as dynamic as you like with the
registries under your own deployment control.
Gr. Sim
That's seems a fair assumption, it would make development simpler to
begin with, if we want to, we can add text key's later.
We have a number of choices of existing software, but if we pick from
two Java based software stacks, there is jmdns and waiter.
Jmdns is currently developed but doesn't have much in the way of unit tests.
Waiter hasn't been actively developed in two years, however it has
comprehensive unit tests.
Both are Apache 2 Licensed projects.
Seeing as we're not interested in Multicast DNS, we're probably better
off utilising Waiter's source and integrating only the functionality we
need into River. I'll ask the original author if he's happy to donate
some code.
Regards,
Peter.
