W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: HTTP Batch Request Draft

From: Patrick McManus <mcmanus@ducksong.com>
Date: Wed, 10 Jun 2009 09:16:04 -0400
To: James M Snell <jasnell@gmail.com>
Cc: Daniel Stenberg <daniel@haxx.se>, Bjoern Hoehrmann <derhoermi@gmx.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1244639764.25560.12.camel@tng>
"Once the batched request messages have been processed, a single HTTP
   Batch Response message is created wherein each part contains the HTTP
   Response Messages."

This seems to mean the server cannot begin to generate any response
until all portions of the request have been received. That would seem to
recreate the same head of line blocking problem on a connection we
already have with pipelines. 


   "To simplify client processing of the response, the ordering of
   response messages in the Batch Response SHOULD match the ordering of
   request messages in the Batch Request."

huh? The value I see in your proposal is that it allows out of order
responses which could improve latency for requests that would other wise
be "stuck-in-line". So why would you recommend against your strongest
(only?) feature. The client has to correlate the ID's anyhow - so its
not like you've made it easier.  


hth.

-- 
PenBay Networks
VOIPRecorder - Record Calls Made with Vonage(tm) on Your Computer!
www.penbaynetworks.com
Received on Wednesday, 10 June 2009 13:16:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT