Fwd: Patch update: netty-242

[rzo]

Hello,

The idea of this patch is to avoid the http overhead, thus reducing 
communicaiton to a minimum.
You could extend this patch to run over http, but for that I would 
recommend using the hessian servlet with tomcat.
I have not done benchmarks tomcat vs netty HttpDecoder, but tomcat is 
very efficient, it supports NIO and APR
and implements all you need concerning security and authentication. With 
netty you will have to implement it on your own.
A few years ago I benchmarked hessian rpc on jetty and tomcat and 
decided to
go with tomcat.

Maybe dumb question: why http ? If you want asynchronous RPC you will 
either need some asyncrhonous http on the
client side (for example: 
http://docs.safehaus.org/display/ASYNCWEB/Home) you will need support 
for asynchronous http,
which requires non-standard framework.

regards

-- Ron


On 13.01.2010 00:47, fatbatman wrote:
> Hi Ron,
>
> I just had a quick look and it seems very nice.  I'll have a quick play over
> the next few days and get back to you with some feedback.
>
> Could it be run over Http(s) by making HessianRPCReplyDecoder extend
> HttpMessageEncoder? etc I believe in that case a second connection would be
> needed to handle the continuations.
>
> regards
>
> James
>