[Springframework-developer] HttpInvoker

[Martin K. <Mar...@St...>]

Getting notice of the HttpInvoker implementation yesterday,
I would like to make some additional suggestions.

I programmed such a solution half a year ago, using=20
serialization for remote procedure calls. I tried to contribute
the code to Spring those days, but I wrote about the request=20
in the sourceforge forum only and got only one reply those=20
days :-(.

Never the less, such a simple remoting solution proofed to be=20
usefull outside the areas of Spring. It works well for=20
client<-->server communication in general and=20
applet<-->server communication in special. The client=20
API's footprint is only about 5KB to 6KB so it is predestinated=20
for mobile/applet point-to-point communication.=20

Also I think, in most areas a socket-driven solution is more=20
preferable than a http one, since session management feels
more natural then http requests/http sessions, and it establish
a two-way communication, but maybe this is just more like=20
a habbit.

Since I am currently using Spring RC 1.1, I had noticed=20
that Spring 1.1 is most likely to become final these days,=20
I guess I am maybe late, but here is a summary about I=20
finally want to suggest:

* I would like to see such a 'simple RPC' solution to be
exposed as an independent API.=20
* It should also provide socket-driven connections=20
(two-ways connection).


So what do you folks think about this?


Bye,

Martin (Kersten)