HTTP1.1 Pipelining

[brunodecarvalho]

Consider 3 requests from your client: A, B and C.

Since A, B and C arrive in order at the server, they generate three
MessageEvent (UpstreamMessageEvent actually) which will hit
YourChannelHandler in that same order. Assuming that YourChannelHandler
never delegates work to other threads, responses to those requests will also
be written in order.

So as far as I can tell, the answer is yes. Netty supports Http1.1
pipelining both at client and server side *IF* you don't delegate work to
your own threads. If you do, it's your responsibility to ensure they're
written back in the correct order.

I've ran a few tests once (GET /1, GET /2, GET /3, ..., GET /N and the
response body would contain the number of the requested URI) and I never got
out of order responses, not matter how many clients I threw at the server.

I can share this code, if you want.


Cheers,
  Bruno
-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/HTTP1-1-Pipelining-tp5320720p5333805.html
Sent from the Netty User Group mailing list archive at Nabble.com.