[rabbitmq-discuss] RPC

Fri May 20 23:56:02 BST 2011

Hi Kane,

also a very interesting implementation.  Nice use of anonymous class/types.
Once you get the channel setup out of the way, you get RPC in only a few
lines of code.

For the client side does the server side "handleStringCall" drop "handle"
through convention?  Just tracing this through visually.  I'm not a java
guy.

-Steven

On 20 May 2011 23:34, Steven Taylor <taylste at gmail.com> wrote:

> Hi Simone,
>
> thanks.  That's really helpful.
>
> Also, I like your "Run<ProjectX.Runner>(args);" idea.  That's quite neat.
> -Steven
> On 20 May 2011 19:15, Simone Busoli <simone.busoli at gmail.com> wrote:
>
>>    Hi Steven, I've written the tutorials in C# here
>> http://code.google.com/p/mexexp/source/browse/trunk/RabbitMQ
>>
>> On Fri, May 20, 2011 at 19:58, Steven Taylor <taylste at gmail.com> wrote:
>>
>>> Is there an example for the RpcClient and the RpcServer classes
>>> (SimpleRpcClient / SimpleRpcServer).  Is it advistable to use these classes?
>>>
>>> Alternatively, there's this tutorial
>>> http://www.rabbitmq.com/tutorials/tutorial-six-python.html ... but I
>>> don't know python.  I'm not following the "rpc_client.py" portion.
>>>
>>> Here's a guess.  def on_response is defining an event.
>>>
>>> "return int(self.response)" waits until the result of "def on_response"
>>> is fired?  If the correlation match fails, execution doesn't return to "
>>> return int(self.response)"
>>>
>>> btw: I shouldn't guess.
>>> Is there a C# or Java version?
>>>
>>> thanks,
>>> -Steven
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110520/e4491b81/attachment.htm>