Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")

Thanks for everyone who has replied to this thread.

Given that valid use cases do exist and the current HTTP spec hasn't
explicitly disallowed concurrent bi-directional communication, I have submit
a draft document as "Implications of Full-Duplex HTTP (
http://tools.ietf.org/id/draft-zhu-http-fullduplex-01.txt)". The purpose of
this draft is to encourage public adoption of full-duplex HTTP and as well
to help incorporating full-duplex HTTP into other open protocols.

Comments/corrections are very much welcome!

- Wenbo
<http://tools.ietf.org/id/draft-zhu-http-fullduplex-01.txt>

On Wed, May 19, 2010 at 12:50 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

> On 17.05.2010 02:30, Wenbo Zhu wrote:
>
>> ...
>>
>> A more general question is how well proxies support chunk-encoded
>> requests today, since browsers don't generate chunk-encoded requests.
>> Would like to hear your experiences on this
>> ...
>>
>
> My company used to work on a WebDAV client component in SAP Netweaver's
> Knowledge Management (for connecting remote WebDAV servers). We certainly
> used chunked encoding in requests (serializing WebDAV XML). We occasionally
> had issues with that, but as far as I recall that was because of broken
> origin servers (subsequently being fixed), not proxies.
>
>
> Best regards, Julian
>