[Standards] s2s and gracelessly broken streams

Peter Saint-Andre stpeter at jabber.org
Wed Mar 28 02:57:41 UTC 2007

Mridul wrote:
> Hi,
>   Is there any best practices on how to handle broken s2s connection ?
> Two primary cases come to mind :
> 1) Remote server went mia due to some transient network/other jitter and 
> recovers after "some" time (assume enough delay to cause tcp close) : so 
> contacts are still available.
> 2) Remote server went down and came back up after "some" time : so 
> contacts are no longer available.
> (Another condition could be server closing the inbound/outbound socket 
> after some delay.)
> In these cases, assume that unavailable presence was not sent.
> How is contact's presence expected to be treated on the user's server ?

Good question. I'd be curious to hear how current implementations handle 
this. The options are not exactly appealing. :)


Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070327/995cb68b/attachment.bin>

More information about the Standards mailing list