David Sowder (Zothar) wrote: > chat/Alice and chat/Bob are not separate services. Separate users would > be handled at a higher level. All chat clients of a particular type > would use the same N2NM id number.
So every service will have to deal with demultiplexing different users' messages? > Bonjour generally assumes that either everyone is on the same broadcast > domain or that there is a centralized name lookup service available. Sorry, I should have been more specific. Multicast DNS and DNS service discovery are two separate parts of Bonjour - I'm talking about DNS service discovery, which doesn't require multicast or a centralised lookup service. It's just a way to map service names to port numbers. > I > believe we have to use the IANA approach because we don't want two > separate "clouds" becoming connected to be a complex matter. I don't understand what you mean by clouds - I'm not talking about multicast, just a way for a node to look up service ports on a peer, to avoid the need to keep a centrally managed list of ports. > As for easily deploying new services, new services would simply use an > ID out of the experimental range until a dev with commit access could be > contacted, a process which is an IRC channel and a few minutes or hours > away generally, unlike the real IANA, which I believe to be an email > message or two and maybe a few days or weeks away. True, it's not unmanagable - just unnecessary. :-) Cheers, Michael
