On 21/10/10 16:44, Kevin Smith wrote:
I've heard that suggested before, but after consideration I think the
server is the sensible place to deal with this.
The exchange:
<client> Can I be bob please?
<server> No.
<client> Can I be bert please?
<server> No.
<client Can I be beatrice please?
<server> No.
<client> Can I be euhal.uba.ul339a938udleul.acgruh.u please?
<server> Yes.
<client> Thanks!
Seems pointless compared to
<client> Can I be bob please?
<server> No, but I can let you be euhal.uba.ul339a938udleul.acgruh.u instead.
<client> Thanks!
Oh, I'm not disagreeing with that! I don't think the server should ever
refuse to let you connect due to a resource conflict: I think it should
either assign you a resource, or boot the connection whose resource
you're conflicting with. I prefer the latter, as I said in my original
mail. :)
--
Will
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
