[Twisted-Python] Roxen Community: RFC 3091 Pi Digit Generation Protocol (Informational)
![](https://secure.gravatar.com/avatar/7b5d5760f7eb6fb775f45b41fbf1e6b2.jpg?s=120&d=mm&r=g)
We have *got* to support this protocol: <http://community.roxen.com/developers/idocs/rfc/rfc3091.html>
![](https://secure.gravatar.com/avatar/e8d7e03b9981c937597d9bf9ef1f704b.jpg?s=120&d=mm&r=g)
As almost every secure Internet protocol requires a highly accurate value of Pi in order to function correctly, it is imperative that clients only use a trusted PIgen server. The imminent collapse of the Internet is assured if this guideline is not strictly followed. Hilarious. =) On Wed, Sep 26, 2001 at 05:18:53PM +0200, Itamar Shtull-Trauring wrote:
-- Chris Armstrong | carmstro@twistedmatrix.com | cjast3@robert-morris.edu Web Page: http://purl.org/net/ChrisArmstrong
![](https://secure.gravatar.com/avatar/3477a9de290ec6d77129af504faa1c0b.jpg?s=120&d=mm&r=g)
On Wed, 26 Sep 2001, Itamar Shtull-Trauring <lists@itamarst.org> wrote:
We have *got* to support this protocol:
<http://community.roxen.com/developers/idocs/rfc/rfc3091.html>
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". -- The Official Moshe Zadka FAQ: http://moshez.geek The Official Moshe Zadka FAQ For Dummies: http://moshez.org Read the FAQ
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
On Friday, September 28, 2001, at 05:35 AM, Moshe Zadka wrote:
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/
![](https://secure.gravatar.com/avatar/3477a9de290ec6d77129af504faa1c0b.jpg?s=120&d=mm&r=g)
On Fri, 28 Sep 2001, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
I can't be sure. Document it, I'll try and implement the RFC, and I'll see if there is something missing... -- The Official Moshe Zadka FAQ: http://moshez.geek The Official Moshe Zadka FAQ For Dummies: http://moshez.org Read the FAQ
![](https://secure.gravatar.com/avatar/7b5d5760f7eb6fb775f45b41fbf1e6b2.jpg?s=120&d=mm&r=g)
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.
![](https://secure.gravatar.com/avatar/e8d7e03b9981c937597d9bf9ef1f704b.jpg?s=120&d=mm&r=g)
As almost every secure Internet protocol requires a highly accurate value of Pi in order to function correctly, it is imperative that clients only use a trusted PIgen server. The imminent collapse of the Internet is assured if this guideline is not strictly followed. Hilarious. =) On Wed, Sep 26, 2001 at 05:18:53PM +0200, Itamar Shtull-Trauring wrote:
-- Chris Armstrong | carmstro@twistedmatrix.com | cjast3@robert-morris.edu Web Page: http://purl.org/net/ChrisArmstrong
![](https://secure.gravatar.com/avatar/3477a9de290ec6d77129af504faa1c0b.jpg?s=120&d=mm&r=g)
On Wed, 26 Sep 2001, Itamar Shtull-Trauring <lists@itamarst.org> wrote:
We have *got* to support this protocol:
<http://community.roxen.com/developers/idocs/rfc/rfc3091.html>
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". -- The Official Moshe Zadka FAQ: http://moshez.geek The Official Moshe Zadka FAQ For Dummies: http://moshez.org Read the FAQ
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
On Friday, September 28, 2001, at 05:35 AM, Moshe Zadka wrote:
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/
![](https://secure.gravatar.com/avatar/3477a9de290ec6d77129af504faa1c0b.jpg?s=120&d=mm&r=g)
On Fri, 28 Sep 2001, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
I can't be sure. Document it, I'll try and implement the RFC, and I'll see if there is something missing... -- The Official Moshe Zadka FAQ: http://moshez.geek The Official Moshe Zadka FAQ For Dummies: http://moshez.org Read the FAQ
![](https://secure.gravatar.com/avatar/7b5d5760f7eb6fb775f45b41fbf1e6b2.jpg?s=120&d=mm&r=g)
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.
participants (4)
-
Chris Armstrong
-
Glyph Lefkowitz
-
Itamar Shtull-Trauring
-
Moshe Zadka