[ejabberd] XEP-0045 Implementation

C00I90WN c00i90wn at litestep.com
Sun Nov 26 06:44:28 MSK 2006

According to the XEP, the MUC should allow multiple joins to the room if the
bare jid are the same, is it possible to see a fix for mod_muc to act
accordingly with the XEP?

7.1.10 Nickname Conflict
> If the room already contains another user with the nickname desired by the
> user seeking to enter the room (or if the nickname is reserved by another
> user on the member list), the service MUST deny access to the room and
> inform the user of the conflict; this is done by returning a presence stanza
> of type "error" specifying a <conflict/> error condition:
> Example 28. Service Denies Access Because of Nick Conflict
> <presence
>     from='darkcave at macbeth.shakespeare.lit'
>     to='hag66 at shakespeare.lit/pda'
>     type='error'>
>   <error code='409' type='cancel'>
>     <conflict xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
>   </error>
> </presence>
> However, if the bare JID (<node at domain.tld>) of the present occupant
> matches the bare JID of the user seeking to enter the room, then the service
> SHOULD allow entry to the user, so that the user has two (or more) in-room
> "sessions" with the same roomnick, one for each resource. If a service
> allows more than one occupant with the same bare JID and the same room
> nickname, it SHOULD route in-room messages to all of the user's resources
> and allow all of the user's resources to send messages to the room; it is up
> to the implementation to determine how to appropriately handle presence from
> the user's resources and how to route private messages to all or only one
> resource (based on presence priority or some other algorithm).

Best Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jabber.ru/pipermail/ejabberd/attachments/20061126/322784ab/attachment.htm

More information about the ejabberd mailing list