Re: [Twisted-Python] Twisted Trac filters my messages as Spam when trying to update ticket #8102

2015-11-16 Thread Glyph Lefkowitz
> On Nov 16, 2015, at 12:43 PM, Paweł Miech wrote: > > I submitted some patches yesterday, got review from Adi and today I tried to > respond. However I'm not able to respond because all my submissions are > marked as spam and blocked by SpamBayes with super high probability. I wonder > how m

Re: [Twisted-Python] Streaming HTTP

2015-11-16 Thread Glyph Lefkowitz
> On Nov 16, 2015, at 8:03 AM, Michael Schlenker wrote: > > One topic: What should happen if the sender sends malformed data (e.g. > content-length: 100 and sending 200 bytes body). I would usually want to > know if the sender is broken instead of getting a responseComplete() > that claims every

[Twisted-Python] Twisted Trac filters my messages as Spam when trying to update ticket #8102

2015-11-16 Thread Paweł Miech
Hello, I submitted some patches yesterday, got review from Adi and today I tried to respond. However I'm not able to respond because all my submissions are marked as spam and blocked by SpamBayes with super high probability. I wonder how many other users experience that problem? Can you please fi

Re: [Twisted-Python] Twisted Web at 630k reqs/sec

2015-11-16 Thread Tobias Oberstein
Are you sure IOCP is able to share sockets between process? It would be great if you can share some info about this. I only use No, I am not sure. But this SO reply seems to suggest http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they

Re: [Twisted-Python] Streaming HTTP

2015-11-16 Thread Louis D. Burr
Hi Cory, > On Nov 13, 2015, at 6:36 AM, Cory Benfield wrote: > > Folks, > > # Problem Statement > > Thanks for your feedback on my HTTP/2 questions. I’ve started work > implementing a spike of a HTTP/2 protocol for twisted.web. I’m aiming to have > something that works in at least some cases

Re: [Twisted-Python] Streaming HTTP

2015-11-16 Thread Michael Schlenker
Hi, sounds like a good idea. One topic: What should happen if the sender sends malformed data (e.g. content-length: 100 and sending 200 bytes body). I would usually want to know if the sender is broken instead of getting a responseComplete() that claims everything is fine. We simply subclassed t