Hi,
Since I'm getting the following packet, the reason is
StreamErrorConflict.
<stream:error xmlns:stream='http://etherx.jabber.org/streams'>
<conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
</stream:error>
Does that make sense on all server implementations?
(We're using Openfire.)
Thanks,
Rafi Rainshtein
Clients Team Leader
Phone: +972.3.976.7631
Fax: +972.3.976.7671
rrainshtein@xxxxxxxxxxxxx
MyRoom.interwise.com
-----Original Message-----
From: Jakob Schroeter [mailto:js@xxxxxxxxxx]
Sent: Wednesday, July 11, 2007 13:11
To: gloox-dev@xxxxxxxxxx
Subject: Re: [gloox-dev] Identifying Kick-out
On Wed Jul 11 2007, Rafi Rainshtein wrote:
> Hi,
>
> I meant kick out on the TCP level. Obviously it is handled by
> onDisconnect() but the question is whether it is possible to detect
> being kicked out rather than a network error for example. Does the
> server/XMPP have any specs about it?
The server should send a <stream:error> before closing the connection.
The
connection error is ConnStreamError in this case and you can check for
the
actual reason with ClientBase::streamError().
cheers,
Jakob