-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/22/12 6:18 AM, Bartosz Małkowski wrote: > Hi! > > I have a question about changing nickname by MUC Room occupant, > when he is connected from one bareJid to room as few nicknames. > > Suppose that we have: nickname1 (from resources: /resource1, > /resource2) nickname2 (from resource: /resource3) > > let /resource1 change nickname to 'nickname2' > > I think that MUC can skip inform other occupants about it, but what > about inform /resource1? > > MUC can't send <presence type='unavailable' from='nickname1' > to='/resource1'>…<status code='303'/> becuase /resource1 removes > 'nickname1' from occupants list (this is wrong, because /resource2 > is still known as 'nickname1') > > How to inform client that changing nickname is finished? How client > should recognize that nickname is changed?
Heh, good question. There are a lot of complexities about allowing multiple resources to share the same roomnick. We started to add a bunch of text to XEP-0045 about this, then realized that it probably requires a separate specification. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA2aOMACgkQNL8k5A2w/vy1fQCgwiWB7Q8n7BpLu/owPjauNB/j lDMAoMu2Gn3eOn3pCOx6za91K7ASIQ/w =zazI -----END PGP SIGNATURE----- _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
