QXmppServer seems not to handle </stream:stream> about qxmpp HOT 4 CLOSED

You are correct, and the behaviour you describe applies both to QXmpp based clients and servers. I have made a change to QXmppStream so that the end of the incoming stream triggers closing the outgoing stream. Can you please confirm this fixes your issue?

Re-reading the RFC brings to mind another issue: to be fully compliant with the RFC we should not close the TCP socket until the incoming stream has been closed. However I am reluctant to make this change at this point as I fear it will potentially cause regressions in the form of "hung" connections.

from qxmpp.

Thank you for the fix - you were too fast, I already was preparing a pull request...
Your solution looks similar to my approach, however I'm going to test it this afternoon and leave a reply.

I agree with your concern regarding the TCP socket: For instance (if my observations are correct) the client library jabber-net has a bug and doesn't close the TCP connection after receiving the closed strem.

from qxmpp.

The test was successful.
(The jabber-net based client keeps a connection in state CLOSE_WAIT, but this is a problem of jabber-net and not qxmpp.)

from qxmpp.

Good news!

from qxmpp.