On Friday, September 28, 2001, at 05:35 AM, Moshe Zadka wrote:

On Wed, 26 Sep 2001, Itamar Shtull-Trauring wrote: This isn't a joke. I feel that there are significat problems with the protocol/transport communication that make implementation of something like this needlessly hard. Specifically, I want the protocol to be notified if doWrite() was called when the buffer is empty, and for the protocol to notify the transport that it always "wants to write".

That's what the Producer mechanism is for. You can also have your protocol be your producer, if you want. What's the problem with that? Is this just a documentation issue or is there something I'm missing? -- ______ you are in a maze of twisted little applications, all | |_\ remarkably consistent. | | -- glyph lefkowitz, glyph @ twisted matrix . com |_____| http://www.twistedmatrix.com/

Moshe Zadka wrote:

I can't be sure. Document it, I'll try and implement the RFC, and I'll see if there is something missing...

I think you just need to self.registerProducer(self, 0), and then every time the protocol needs data it will call self.resumeProducing(). The docstrings in abstract.FileDescriptor are pretty good.