> > If you need programmable message routing that scales with your > imagination, then I recommend a message broker like RabbitMQ [1] or 0MQ [2]. >
I thought RabbitMQ was more of a "one way" thing for client messages to go to a server "sink". But a quick look at their web site shows they have publish/subscribe and a tutorial on it HERE <https://www.rabbitmq.com/tutorials/tutorial-three-dotnet.html>. I'll check this out later. It's another candidate! - *Greg K*
