Someone contacted me offlist as follows: ###
The HTTP standard says that non-idempotent methods should not be pipelined: Clients SHOULD NOT pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see section 9.1.2). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to send a non-idempotent request SHOULD wait to send that request until it has received the response status for the previous request. But the BOSH standard uses POST + pipelining. Doesn't this break the HTTP standard? ### However, it seems to me that BOSH has methods for ensuring that premature termination of that transport connection will not lead to indeterminate results (via the 'rid' attribute), so we have mostly good reasons for not adhering to the SHOULD NOT in RFC 2616 (which is repeated in draft-ietf-httpbis-p1-messaging). Thoughts? Peter -- Peter Saint-Andre https://stpeter.im/
