Hi,
On Oct 6, 2008, at 9:07 PM, Justin Karneges wrote:
On Monday 06 October 2008 12:15:56 Pedro Melo wrote:
cool, you should name the connections. I think we all agree on that.
I'm just suggesting that you use the name attribute of the disco
<identity> to do it.
That's what he is there for.
I'm reminded of the DNS-SD specification. I suggest reading section
4.4:
http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt
The authors (likely Cheshire here) argues that there is not much
point in
using an ugly hex value for the real identifier, and a discoverable
friendly
name, when you could just use the friendly name as the real
identifier in the
first place.
I've started to read the dns-sd.txt you pointed me to, and although I
haven't finished yet, I think you analogie breaks down pretty quickly.
If I had to map DNS-SD to XMPP, I would say that DNS-SD is
XEP-0030+XEP-0115 and XMPP Core is IP.
You JID, including the resource, is an network address for a service.
The same way you don't expect the printer._tcp.your.domain to change
when the IP changes, I also expect my "Work" resource with its
personal file server not to change when the connection switches from [EMAIL PROTECTED]
/dasfkjagkagd to [EMAIL PROTECTED]/9823987892374.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
