I understand your desire to keep as much of the functionality as possible within a few programs. Keith and Dan provide solutions below that are what I would provide too. If this is a webapp, a 3rd approach would be to have your observer grab the job from a webserver in serialized xml/json/whatever format, but that would be a pretty serious restructuring.
The reason I suggested RabbitMQ as a potential partial solution is semantics, the short is beanstalkd has an anycast semantic while rabbitmq has a multicast semantic. There is a thread a while back about Second Life's MQ ratings, in which i spend way too many words on this subject. Good luck, Erich --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
