[rabbitmq-discuss] Implementation / Specification Stability?

[Landon Fuller]

On Oct 20, 2007, at 5:15 AM, Ben Hood wrote:

> This is currently possible. I am using a wrapper around the Java
> RpcClient to that puts Hessian encoded calls onto a queue that gets
> consumed by an Erlang rpc handler, which in turn decodes the Hessian
> payload, invokes a service API, encodes the response which goes back
> out to the Java client. Pretty simple stuff really, though what I have
> done on the Java side is a rough cut, because I've been concentrating
> *productizing* the Erlang side of things. I envisage at some stage to
> produce a SCA connector to hide this plumbing from the application
> code, but I'm not going to harp on about what is currently vapourware.

Neat -- This is roughly what I've got wired up, amusingly, also using  
Hessian.

Have you delved into security?  That's my next concern -- how to  
prevent a client/peer from reading requests off of the RPC service  
queue?

Cheers,
landonf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20071022/f40c4888/attachment.pgp