[Standards-JIG] Closing idle streams

Julien PUYDT julien.puydt at laposte.net
Thu Jun 1 18:57:28 UTC 2006


Peter Saint-Andre a écrit :
> Carlo v. Loesch wrote:
>> 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.

I always thought the rationale for the close-socket-on-stream-error 
behaviour was that since the stream was tainted, it was no longer 
suitable for service.

Snark on #ekiga



More information about the Standards mailing list