Turned out this was my fault on the client side. When leaving a room I was sending the presence to the room's bare JID and ignoring the nick. A closer reread of XEP-0045 based on this thread pointed me in the right direction :)
dan On Fri, Mar 8, 2013 at 10:42 AM, Daniel Dormont <[email protected]> wrote: > Thanks, that's what I thought. In my current implementation (an > admittedly slightly hacked ejabberd-2.1.10) I'm not seeing that - the > other occupants are seeing the broadcast right away. Ok, I'll see what > I can figure out from the code. > > dan > > On Fri, Mar 8, 2013 at 10:32 AM, Kevin Smith <[email protected]> wrote: >> On Fri, Mar 8, 2013 at 3:30 PM, Daniel Dormont <[email protected]> >> wrote: >>> I have a question about the expected behavior of multi-session nicks >>> in a semi-anonymous room. Specifically, if user A joins a room where >>> user B is already present with two sessions sharing the same nick, >>> user A will only see this nick once in the list of presences sent when >>> they join. But if user B leaves the room in only one of their >>> sessions, that unavailable presence is still broadcast to the room and >>> A sees it. Is there a way in this case for A to know that B is still >>> in the room (but only from one session, now)? >> >> Multi-session, as currently specced, works transparently - you don't >> know that there are multiple sessions associated with someone else's >> nick, and you don't see them leave the room until their last session >> leaves. >> >> /K >> _______________________________________________ >> JDev mailing list >> Info: http://mail.jabber.org/mailman/listinfo/jdev >> Unsubscribe: [email protected] >> _______________________________________________ _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
