Re: [Twisted-Python] Streaming Requests

2017-01-09 Thread Cory Benfield
> On 8 Jan 2017, at 06:44, Mark Williams wrote: > > * Comments? > Will this approach break a public API? Does it sound terrible? Or > good? Please share your thoughts! > > Let's hope 2017 is the year of the streaming request! > > -Mark I’m very excited to see

Re: [Twisted-Python] Streaming Requests

2017-01-08 Thread Mark Williams
On Sun, Jan 08, 2017 at 07:34:53PM -0500, Jean-Paul Calderone wrote: > Hi Mark, > > Thanks for tackling this long-standing issue! > I hope I actually make some progress :) > > He also noted that the Request interface with which HTTPChannel > > interacts is mostly not described by

Re: [Twisted-Python] Streaming Requests

2017-01-08 Thread Jean-Paul Calderone
On Sun, Jan 8, 2017 at 1:44 AM, Mark Williams wrote: > * What? > A new year means renewed ambition. So let's talk about receiving > streaming requests! > > Hi Mark, Thanks for tackling this long-standing issue! I want to start off by responding to just one part of

[Twisted-Python] Streaming Requests

2017-01-07 Thread Mark Williams
* What? A new year means renewed ambition. So let's talk about receiving streaming requests! * Why? Twisted's HTTP server implementation does not allow application code to interact with a request until its body has been entirely received. It also doesn't allow incremental access to