Hi Tony,<br><br>Let me explain it better.<br>I have to handle requests to TCP/IP servers using different protocols (stateful), the idea is to use a common pool of workers (consumers) to where distribute those requests for further processing. Each consumer process (finite state machine session) should handle all the subsequent communication for the request received until coming back to idle state (consumer released).<br>
<br>As far as I understand, RabbitMQ can act as the pool to distribute and route messages to the right consumer process. Can this be handled by RabbitMQ? Any example to share?<br><br>thanks,<br>Luis<br>�<br><br>So RabbitMQ<br>
<br><br><div class="gmail_quote">2009/3/17 Tony Garnock-Jones <span dir="ltr"><<a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a>></span>eful<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Luis,<br>
<div class="im"><br>
Luis Da Silva wrote:<br>
> Is it possible to implement stateful protocols using RabbitMQ (routing,<br>
> memory shared between states,...)?<br>
<br>
</div>I'm not sure what you mean here. Are you talking about state<br>
synchronisation between applications -- a form of<br>
replication/object-caching?<br>
<br>
Regards,<br>
�Tony<br>
<font color="#888888">--<br>
�[][][] Tony Garnock-Jones � � | Mob: +44 (0)7905 974 211<br>
� [][] LShift Ltd � � � � � � | Tel: +44 (0)20 7729 7060<br>
�[] �[] <a href="http://www.lshift.net/" target="_blank">http://www.lshift.net/</a> | Email: <a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a><br>
</font></blockquote></div><br>