I'm not sure if I'm going the right direction here so I thought I'd see what other people thought. I have a server that is running jobs at different intervals. I would like to allow clients to connect to the server and receive events back when jobs are triggered. There will be an unknown # of clients and could be multiple clients started under the same machine / same user. I initially set this up with Rhino ESB using MSMQ and it works with 1 client. If it start up a second client then it seems the messages start to distribute between the two clients. The message will go to either one or the other but not both. Which probably makes sense on how I have it configured. So then I have a couple of questions.
Is there an example configuration somewhere that has 1 server -> X clients where ALL messages from the server get to ALL clients? (bus.Notify()) Secondly.. does each client require it's own queue? If so.. How do I handle a situation where multiple clients are connecting from the same machine (in the scenario of many users connected to one terminal server.)? If each client is using the same queue name then I believe this would be a conflict. Then of course I may also be thinking of the wrong technology here and could possibly switch to something more like WCF. Thanks, Nathan Palmer -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
