[Standards-JIG] Closing idle streams

Peter Saint-Andre stpeter at jabber.org
Wed May 31 15:14:08 UTC 2006


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

Carlo v. Loesch wrote:
> What is the popular or correct way to close an idle connection?
> 
> I noticed some jabberds will send a <connection-timeout/> error,
> then immediately close the socket.
> 
> This seems to be in accordance with the XMPP spec.
> 
> I also noticed some jabberds that would simply shutdown the
> socket without warning.
> 
> This doesn't seem to be in accordance with XMPP.
> 
> One way or the other, closing a TCP socket - instead of asking the other
> side to terminate it - raises the chances of data loss, so it is a not so
> good idea really. Am I missing something?
> 
> I also noticed XMPP isn't very precise on what is to be done
> under this circumstance.
> 
> Has this been discussed before? I looked at the TCP reliability
> discussion, but that doesn't apply to this issue.
> 

You are correct that this is not discussed in RFC 3920. We'll need to
add some text about it to rfc3920bis.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

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

iD8DBQFEfbK/NF1RSzyt3NURAsdcAJ4ogoMk+Xnuxr4x6bSUwaCiLS1cvQCgw+/l
knUeTMSnups5ZifRUrA9OJc=
=5os7
-----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/20060531/ef399bb3/attachment.bin>


More information about the Standards mailing list