Re: [hybi] short term requirements

[Jamie Lokier <[e-mail]>]

Greg Wilkins wrote:
> Salvatore Loreto wrote:
> > This is a call to collect requirements that you think a Short Term
> > solution should meet.
> >
> > Req.   possibility for the intermediaries to access and modify it
> > Req.   it must be usable from multiple (existing) browser
> > Req.   it must be easily to use and accessible from different protocols
> > (e.g. Bayeux, Bosh etc)
> > Req.   it must be easy to deploy in the existing infrastructure
> > Req.   it has really improve the bi-directional communication (not just
> > push from a server to a client)
> > Req.   it has not introduce any security hole
> > 
> > please provide comments, opinions, suggestion.
> 
> 
> I would like to add
> 
> Req.   That there must be a standard way to indicate that a HTTP request is
>        being used for bidirectional purposes, preferably distinguishing
>        streaming and long polling uses.
> 
> This will allow HTTP implementations to avoid pitfalls such as
> pipelining behind long polls, and to warn if limited thread pools
> are exhausted by long held requests.

I agree with Greg, and would like to add that I'm not sure if
"Connection: close" is adequate for that purpose.  It's not as
descriptive, but is it (a) enough for all existing proxies and servers
to behave well; (b) is something more specific to streaming and long
polling useful?

-- Jamie