[Standards-JIG] JEP-0045 and locking room nicknames

Peter Saint-Andre stpeter at jabber.org
Mon Apr 10 23:05:48 UTC 2006

Hash: SHA1

Peter Saint-Andre wrote:
> On Tue, Mar 28, 2006 at 01:12:34AM -0500, Etan Reisner wrote:
>> Let me start by saying that I tried to look up any previous discussion 
>> of this topic on this list as well as on the jabberd list (I was pretty 
>> sure I rememberd there being some) but I couldn't find it. So apologies 
>> in advance if I missed it.
>> For our jabber server at work we are forcing all room nicknames to be 
>> the same as the user portion of their JIDs. Optionally, with '-foo' 
>> appended. (I mentioned this system in a recent email regarding 
>> JEP-0172.) Our current code returns the following presence error if you 
>> attempt to change nicknames while in the room to an invalid nickname.
>> <presence type='error'><error code='406' type='modify'><not-acceptable 
>> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></presence>
>> Is this a correct error for this scenario? I'm asking because it is 
>> causing us some problems, it confuses the clients I have tested it 
>> against.
> Yes, that seems appropriate. Clients may not handle it well because it's
> not specified in JEP-0045, but I'll add that flow to my todo list for
> revisions.

I've added this to my working copy.

How do you handle room joins? Presumably you modify the requested
roomnick on entry. It would be good to add that flow to the JEP as well.


- --
Peter Saint-Andre
Jabber Software Foundation

Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060410/dacec1de/attachment.bin>

More information about the Standards mailing list