[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Netty HTTP transport

[trustin]

"ataylor" wrote : anonymous wrote : The plan is to write a codec for both client and server side, which means we need two encoders and two decoders - HttpRequestEncoder, HttpResponseEncoder, HttpRequestDecoder and HttpResponseDecoder. So, it's writing something from scratch. 
  | 
  | I guess the encoder just writes the headers followed by the body but with thge decoder we need towait for the whole of the body to be delivered before translating the content into a nettybuffer?

Yes.  That's why implementing an encoder is relatively easier than implementing a decoder.

Netty provides a couple ways to write a decoder easily.  For example, take a look at this: http://tinyurl.com/57dtcb

ReplayingDecoder simplifies it even further.  It allows you to write a decoder just like writing a blocking decoder: http://tinyurl.com/5tkwnw



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183761#4183761

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183761