Hi,
Quoting Di Yao <dyao750@xxxxxxxxxxxxxxxxxxx>:
[...]
[A] Closing message sessions
1) How to know when a user signed off -- does the user need to send a chat
state message with the state set to gone before leaving?
No, please see XEP-0085 for a detailed explanation of chat states.
2) I created two services, S1 and S2. There's a message session between S1
and S2. S1 wants to close message session. What's the sequence of steps to
close the message session on both S1 and S2? I assume to close the message
session I call S1.client->disposeMessageSession(). However, when I call
disposeMessageSession() on both S1 and S2's clients, S2 crashes.
There is no direct relation between two message sessions. I.e. you can
use them on one end but not on the other.
[B] Again I have two services, S1 and S2. S1 created a chatroom and invites
S2 to join. S2's handleMUCInvitation(roomJID, ...) gets called but I wasn't
sure how to join the chatroom so I assume that S2 also creates a chat room
using roomJID. However, when S2 calls join() on this chatroom, S2 crashes.
Here's S2's log message.
Do you have backtraces of the crashes? Which version of gloox are you
using? On which platform?
Please don't re-send messages to the list. It delays a reply, if anything.
cheers,
Jakob
--
gloox-dev mailing list
to unsubscribe:
send a message with subject 'unsubscribe gloox-dev' to minimalist@xxxxxxxxxx