[Standards-JIG] Closing idle streams
stpeter at jabber.org
Thu Jun 1 18:50:28 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Carlo v. Loesch wrote:
> Peter Saint-Andre typeth:
> | Can't a server send the following in the same TCP packet?
> | <stream:error>
> | <connection-timeout
> | xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
> | </stream:error>
> | </stream:stream>
> Unfortunately not, because a stream:error MUST be followed by
> the termination of the TCP connection (4.7.1 rule 1).
It seems more helpful to inform the other side why the stream is being
closed by sending a stream error, rather than sending </stream:stream>
and leaving the other side to wonder why the stream was closed. If that
is true, then it may make sense to relax the rule in 4.7.1 by decoupling
closing of the XML stream from termination of the TCP connection (i.e.,
I wonder if the text really needs to say "MUST close the XML stream and
SHOULD terminate the TCP connection"). Naturally we would need to think
carefully about the consequences of any such change.
Jabber Software Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards