[cl-xmpp-devel] [Fwd: Ending an session]

[Kevin Crosbie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Thanks for the reply David,

David Lichteblau wrote:
> I believe the error message says that </stream:stream> was
> expected, and EOF seen instead. Are you sure the server actually
> sends a closing tag?  Perhaps it just closed the connection.  (It
> would be better to handle that without erroring out, of course.  I
> could try to add an end-of-file condition to cxml that is more
> specific than WELL-FORMEDNESS-VIOLATION for this purpose.)
>

In the second case, that of the server being killed, I think you're
correct.

In the first case, that of a conflict, I used Wireshark and verified
that the server sent:
<stream:error><conflict
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xml:lang=''
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Replaced by new
connection</text></stream:error></stream:stream>

So it looks like it is sending the </stream:stream>

The error:
Error: Document not well-formed: Bad nesting. "stream:stream" / (:EOF)

  [condition type: WELL-FORMEDNESS-VIOLATION]

is thrown, but I wonder is this because the socket is closed by the
server at this point.

>
> Might as well be a bug somewhere in cl-xmpp, of course.

Perhaps cl-xmpp needs to catch the :EOF and throw stream closed or
stop the receive-stanza-loop, something that a cl-xmpp client can deal
with.

Kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFHTqEYEdUcNFP15iMRAu7MAJ9/B4ocaH4UET6IU+W2hjGFtfznOgCeOQzQ
zVmpWC83D2LpubGGJwUU2Qo=
=K5zB
-----END PGP SIGNATURE-----