On 03:06 am, dreid@dreid.org wrote:
>On Jul 2, 2007, at 3:21 PM, Ed Suominen wrote:
>>I have been debugging an odd problem that apparently is arising in
>>web2.stream.FileStream. (...)

>There is a bug, please feel free to contribute a patch.

    http://twistedmatrix.com/trac/ticket/2296

>>As requested by Dialtone, and to borrow liberally from what he  wrote in
>>an IRC chat with me today, web2.stream code is pretty badly tested (...)

>It is conceptually pretty bad, and counter to existing abstractions  in
>Twisted.  I believe there is a bug about this, (...)

    http://twistedmatrix.com/trac/ticket/1937

>>I can't believe that the world's greatest networking platform *still*
>>doesn't have an adequately supported HTTP server!

    http://twistedmatrix.com/trac/milestone/Web2-Gold-Master

>I'm sorry.

While this is unfortunate, I don't think that there's really any reason to apologize.  This is a volunteer effort all around, and it's as much my fault (and Ed's) that such a server doesn't exist.

In fact, David, if there are any people whose fault it *isn't*, it would be you and dialtone.  Thank you for your sustained (albeit intermittent) efforts to get this done.  (Of course, the bears and I reserve the right to hassle you mercilessly to complete it.)

As I've annotated here, the issues that Ed outlined in his email are pre-existing, with tickets describing them.

If anyone out there shares his frustration and would like to help us along towards a supported web2 release, or any other part of Twisted for that matter, just have a look at the Twisted tracker and steal a ticket from some of the obviously overcommitted and overworked maintainers.  The milestone link I posted is the best start for web2.

Many of those tickets are underspecified, but don't let that stop you.  If you find a ticket that you think sounds interesting but you don't understand how to proceed on it, feel free to comment and ask for clarification - it is often far easier for a maintainer to respond to a prompt for some answers to questions than to drive tests, documentation, and code all the way through the review process.