On 23 Mar 2005, at 16:00, Justin Karneges wrote:
On Wednesday 23 March 2005 06:27 am, Julian Missig wrote:On 23 Mar 2005, at 0:31, Justin Karneges wrote:3) stanzas need to indicate both the 'to' and the 'from' (since either workstation might have multiple users. yes, I think we should be forward thinking here).
Ok, this is pretty silly and makes the problem thousands of times harder. DNS-SD lends itself to be used as presence broadcasting, but then you /can't/ use it as presence broadcasting if there are multiple users connected without making /those/ packets insanely complicated too. I don't think that's a problem we should be focusing on at all, because I don't see how it's going to make anything simpler /or/ better.
I don't follow. Existing client code is going to expect 'from' attributes on
incoming stanzas. This means that either 1) the clients have to be hacked to
not care about 'from' attributes on incoming stanzas or 2) clients need to
put 'from' attributes on the stanzas they send out. #2 is not a thousand
times harder than #1.
Supporting multiple users on a single machine might be a thousand times
harder, but you're not forced to do that. A single-user ad-hoc client should
have no trouble interoperating.
I think that for now we should focus on things which DNS-SD has proven useful for. Multiple users advertising the same service on one computer is not one of them, and until the DNS-SD people have a good solution for that (if they care about it at all), I don't think we should.
Unless I've misunderstood how zeroconf works, I thought that you'd announce a
single service regardless of whether or not the service was single- user or
multiple-user. Yes, this probably means that for multiple-users you'd need
an ad-hoc Jabber client daemon. No, I'm not saying anyone has to implement
it that way.
Yes, except that the iChat way of doing this makes a *lot* of sense. I don't know how you're expecting to to distribute presence using DNS- SD, but with iChat, the "service" it's advertising *is* the presence. So this is sort of by definition single-user.
Julian
smime.p7s
Description: S/MIME cryptographic signature_______________________________________________ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
