[rabbitmq-discuss] "Returning" values

[Alvaro Videla]

Sorry, forgot to "reply all" 

Answer:

Usually you set up a consumer on the client system that act as a callback. So when the job is finished, it inserts a new message in the queue with the status of the process, this message is then retrieved by the client application.

On Mar 29, 2010, at 12:56 PM, Andreas Jung wrote:

> Hi there,
> 
> I am aware that a message queue does not support returning value. Is there a pattern for the following usecase:
> 
> User submits a data set through the browser to the backend application. The backend puts the data into a queue in order to be processed by one of a worker processes running on some other machine taking requests from the queue.
> 
> The client application should be notified or take notice when the data has been processed and get hold of some return value.
> 
> I was thinking for having some client specific 'return queue' where the worker could insert the return value...however the number of queues is limited ( by RAM?) and the number of possible clients may exceed the number of maximum queues....so not a solution..
> 
> Is there a pattern for implementing this usecase with RabbitMQ?
> 
> -aj
> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss