Re: twisted web write to a connection closedfrom client-side

Shouldn't the HTTP protocol implementation (twisted.web.http) itself
respond to connectionLost? 'haps you need to augment that.

-Jared

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, December 11, 2009 3:20 PM
To: Twisted Web World
Subject: Re: [Twisted-web] twisted web write to a connection closedfrom
client-side

On 10:51 pm, [email protected] wrote:
>Hi,
>
>I have a problem: twisted does not indicate/throw exception when user
>has stopped reading the stream via "STOP" browser button (I guess it
>won't do in any other case of connection drop). Is this intended
>behavior and is there any way to detect that the data written to
>request goes nowhere?
>
>I am using twisted web to write HTTP stream that is read form
>asynchronous source continuously. I'm using Resource and
>NOT_READY_YET, then I just do request.write() infinitely until, and
>if, the source stops the stream, then do request.finish().
>If the source does not stop and I stop the stream by hitting browser
>"stop" button - the twisted server continues reading source
>infinitely.
>
>Could not find any information about how connection resets are handled
>by twisted web

I wrote about this recently,

  http://jcalderone.livejournal.com/50890.html

Jean-Paul

_______________________________________________
Twisted-web mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web