Probably talking about shared subscriptions at that point or possibly a dedicated endpoint, like logging, where these messages are sent which then is responsible for publishing the message out again. And yes, I did just reinvent the message broker, but this would be a specialized broker for a particular message or set of messages - not all messages go through it, in other words. Couple that with the lightweight infrastructure of RSB and the load balancer concept and it might work out alright...just a thought...
On Sat, Mar 21, 2009 at 8:48 AM, Ayende Rahien <[email protected]> wrote: > Yes, it would, but it would only go to interested parties. > There is also another issue, how do you subscribe to that? > For that matter, how do you subscribe for a bunch of servers? > The scenarios that I have in mind is a node in the web farm needing to > publish some state change to all other nodes in the farm. > > On Sat, Mar 21, 2009 at 11:32 AM, Corey <[email protected]> wrote: >> >> Notify depending on the number of endpoints could get very chatty. >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
