Re: [jabsorb-user] Re: Pure Java client

[sash...@gmail.com]

Arthur --

I took a stab at abstracting away the transport and made a new release of the client project (r5, yeah!).

Your next step would be implementing plain socket transport, should be very easy at the client side.

For the server side, as Michael notes, you will need to implement the like of your JSONRPCServlet and write your own plain socket server.

I would still look into the Pygmy Server (http://pygmy-httpd.sourceforge.net/) as there seems to be some sort of transport abstraction so you can save some time.

Let me know if you have questions,
-- Sasha

arthur...@gmail.com wrote:

Neither (1) or (2) actually.

A big important client won't allow internal HTTP access between
servers on an internal LAN because of stupid beurocratic policies and
procedures that they will not bend under any circumstances.
But they will allow certain other types of communication, like RMI (I
know, I know it's stupid.  Doesn't make a lick of sense)

Also, would be nice to have a sockets only client for the smaller size
and simplicity, especially for communicating with a C++ json-rpc
client.

For my own personal needs, yes an HTTP to HTTP client that is all Java
would probably work fine.


On Sep 26, 10:50 pm, sasha...@gmail.com wrote:
  

Arthur --I'd also like to see a pure Java to Java client that can run over a Socket not relying on HTTP or even over RMI (I know that might sound silly but it's actually something I need right now, believe it or not.)Let me understand your motivation. Is it that (1) you want to avoid the overhead of full-fledged HTTP server on the listening side or (2) you have some other (ideologic?) problem with HTTP? The only difference I can see between HTTP and plain sockets is ~100 bytes of overhead (can be made less).
If it's #1 then we have been successful using Pygmy server for that purpose (http://pygmy-httpd.sourceforge.net/) -- it's a 50K jar (can be stripped down to 40) so I had no problem using it on the client side.
I'll see if I can hook up a test case in the coming days, with both Java client and Pygmy server.
Regards,
-- Sashaart...@gmail.comwrote:Hi Sasha, Michael and I are still negotiating on how we can come to a consensus on unification and I am hopeful that we can come up with a good solution soon. We are definately interested in integrating the json-rpc-client into jabsorb in some way. In fact I had already created an issue in the tracker for it in response to one of Cyrille's messages: seehttp://code.google.com/p/jabsorb/issues/detail?id=17I'd also like to see a pure Java to Java client that can run over a Socket not relying on HTTP or even over RMI (I know that might sound silly but it's actually something I need right now, believe it or not.) If you don't mind, post your thoughts on the details on how you'd like to contribute in a new Thread.Also on the unification note, I wouldn't mind contributing my little Java client (http://code.google.com/p/json-rpc-client/) to the unified project if you guys are interested. Regards, -- Sasha