<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thank you Drew.<br>
I should have sketched a bit more: I have to compute many<br>
self-contained jobs and then elaborate their results.<br>
Jobs are distributed to many machines and results are sent back to<br>
the Master. The Master should not wait for all the results to be ready<br>
but should start processing as soon as the first one arrives. After<br>
all the results have been collected and processed, everything starts<br>
over with newer data.<br>
<br>
I have implemented a mock example with PB but if I understand<br>
correctly a messaging system would put me to a higher level of<br>
abstraction taking care of many technicalities. I am now looking at<br>
rabbitmq and txamqp, it is a bit hard to find some documentations but<br>
slowly i am getting the full picture.<br>
<br>
Thanks Jacopo<br>
<br></blockquote><div>Hi Jacopo,<br>this article problably can give you a big picture<br><a href="http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/">http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/</a><br>
AMQP helps you distribute messages to clients that are network connected and can do some jobs when receiving messages.<br>So you can distribute data to your clients using the json protocol to send messages containing data to the clients. And from the computing client you can send back the results always using the json protocol. This only if you don't want to use a central database... but this depends on how you design your app.<br>
HTH<br>Fabrizio <br></div></div><br>