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 another Deferred and returning > the result. Sometimes the read method will return a Deferred, sometimes > it'll just return your data. Without reading the implementation of the > provider you're using it's not easy to know which it'll do when.
Thank you, too. I'll investigate and try to come up with a simple test case, if possible and reasonable. Regards Markus Wanner _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
