I really appreciate your advice on this. Trying to learn about service buses and messaging systems is a lot to take in.
Your recommendations sound on target, but I'm still trying to grasp all the implications. The website would use a one-way bus to send messages to the load balancer. Is the load-balancer a completely separate process? Does it have to exist on the same machine as the web site? Would the encoders have to exist on the same machine as the load balancer? If not, how does that communication work since you cannot read from remote queues? Thank you again. I was really excited to get this working as a cross- process communications system. Now it looks like I've got a lot more learning to do to make it work across multiple machines. On Jun 9, 11:34 am, Corey Kaylor <[email protected]> wrote: > I'm not sure that you'll find another service bus that allows reading remote > queues. I could be wrong. Last time I looked reading private queues on > remote machines for MSMQ was discouraged, maybe that's changed. > > It sounds like you're wanting your encoders to be load balanced. The bus > does have support for this. > > The way I'm seeing meeting your requirements unless I've overlooked > something. > > web application - configured with a message owner of a load balancer > endpoint. > > bus.Send(new Task()); > > load balancer endpoint receives message and is aware of endpoints ready for > work. > > encoding service - receives message given to it by load balancer > > finishes encoding > bus.Reply(new EncodingTaskComplete()); -- 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.
