New Remoting Strategy: HTTP Invoker

[kajism]

Do I need a servlet container on the server side to run this? I think so.

This may be in some cases disadvantage of web services over RMI, because I don't need anything else than plain Java to run RMI.

But if I understand it well there may be problems to setup RMI through firewalls. Right? So that's an advantage of web services that it always runs on a defined port.

Karel

[cjk]

Martin, I am very interested in your socket implementations. That will benefit applet/mobile client a lot. I had played with Hessian and am going to switch to HTTP Invoker. My project has an applet client and I do prefer socket connections so that server side can track conversations and push messages to applet easily.

Is there a way that I can get a copy of your code? Thanks.

[jbetancourt]

The HttpInvoker is pretty amazing. I was surprised that it worked as described. Of course, it took a few hours until I puzzled out what not to do. But, it really was just changes to bean config files and three lines in the web.xml file. That rocks.

It and the other remoting approaches via Spring really show how powerful the AOP/DI combination is. The forthcoming JMX will be big icing on the cake.

Of course, my effort was a demo and proof of concept, and no one bought into the light-weight remoting approach. The ole Butsitis syndrome perhaps.