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

[trustin]

"ataylor" wrote : "trustin" wrote : 3) There's no need to implement HTTP codec to support large chunk of data directly, which means a HttpRequest.getContent() can just return a complete ChannelBuffer instead of a special stream type.
  | 
  | Then we just pass on the buffer in the usual fashion.

Yes.

"ataylor" wrote : "trustin" wrote : However, Chunked encoding should be supported instead to enable COMET, which will eventually allow us to use HTTP as a connection-oriented socket. (Bill Burke is also interested in this.) 
  | 
  | Do we need to support this for the first implementation?

I don't think so.  It can be done after the basic implementation is done.

"ataylor" wrote : "trustin" wrote : Once, this codec is ready, I think implementing a highly customized HTTP server shouldn't be difficult at all. WDYT? 
  | 
  | yes, I think if we concentrate on getting the message model complete we can go from there.

Cool.  :)

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

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