Hi,
David Reid wrote:
> I think this probably has something to do with the fact the IByteStream.read
> may optionally return a Deferred making it quite easy to write code that
> accidentally chain Deferreds to infinity and beyond. Such as if you're
> calling IByteStream.read in the callback of an
Hi,
Jean-Paul Calderone wrote:
> I haven't looked at how web2 handles IByteStream providers, but my first
> guess would be that this is an example of a somewhat common bug where
> Deferreds are chained to an arbitrary length based on application data
> and when there's too much application data, t
On Thu, Mar 5, 2009 at 7:45 AM, Jean-Paul Calderone wrote:
> On Thu, 05 Mar 2009 16:20:27 +0100, Markus Wanner
> wrote:
>
>> Hi,
>>
>> I'm trying to stream longish data via web2, but experience sudden stalls
>> in data transfer, followed by a connection abort after a certain
>> timeout. I can't c
On Thu, 05 Mar 2009 16:20:27 +0100, Markus Wanner wrote:
Hi,
I'm trying to stream longish data via web2, but experience sudden stalls
in data transfer, followed by a connection abort after a certain
timeout. I can't completely reproduce the issue, yet, but figured that
the size of the blocks I'
Hi,
I'm trying to stream longish data via web2, but experience sudden stalls
in data transfer, followed by a connection abort after a certain
timeout. I can't completely reproduce the issue, yet, but figured that
the size of the blocks I'm returning via the stream's read method
affects the failure
