[Standards-JIG] Closing idle streams

Peter Saint-Andre stpeter at jabber.org
Thu Jun 1 16:51:19 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carlo v. Loesch wrote:
> In the meantime, since the new stream closing technique needs
> to be formalized, 

You mean no connection-timeout error?

> I worked out a little 'Best Practice' and
> would like to hear any comments before submission. In particular
> should I add a "How Not to Close an Idle Stream" or is it
> sufficiently redundant?

> 1. Introduction
> 
>    RFC 3920 [[17]1] offers several ways on how to terminate an XMPP
>    stream, but doesn't always make a clear statement which one to take.
>    This can lead to faulty implementations. In particular, closing a
>    stream that hasn't been in use for a while is very often achieved
>    using a connection-timeout error, then closing the socket. This can
>    lead to loss of data. 

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>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEfxsHNF1RSzyt3NURAkuTAJwIe2BkMhmOYKlW9HTXPQYHMyJgGQCfXKEt
Otyq2C0UNjFXWCZZRJkQh9A=
=idZp
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060601/1cc1fea6/attachment.bin>


More information about the Standards mailing list