I don't think introducing a dependency on the load balancer for the subscription storage is the right place for this. Reasoning is that rhino queues is load balanced via hardware. It is probably better to create a shared storage between them, either SQL, Raven, etc.
On Wed, Dec 14, 2011 at 6:44 AM, whut <[email protected]> wrote: > Lets have loadbalancer ALB with two servers A1 and A2. If we then > start another server B, that subscribes to event from A, both A1 and > A2 will have info about that in their subscribers subqueues. But if we > then add another A server, lets call it A3, it will not know about > such subscriptions and will have empty subscribers subqueue. > > I believe that A3 should be able to publish events even if it started > long after B. ALB should store all subscriptions, and sent them to A3 > when it starts. > > What you think about it? > > -- > 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. > > -- 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.
