Does Rhino ESB support publishing messages with a priority? I hesitate asking because I can honestly see the reasons for not wanting to do so. Though, I actually have a specific reason why I want one. I'll try to be clear with a better example.
I have RegularWork and SpecialWork. SpecialWork is a very large amount of work that I need to do very quickly. It doesn't happen often, but when it does it is extremely large and has to turn around quickly. For that reason I have workers that subscribe only to SpecialWork messages. Also, during the day I may have periods of time where RegularWork is idle and I'd like to configure that worker to subscribe to RegularWork and SpecialWork. The idea being that when there is no RegularWork to be done, utilize that worker (that is always running) for SpecialWork. The problem is that if a large number of messages arrive for SpecialWork and then some RegularWork shows up I need to stop processing SpecialWork and continue back on RegularWork only until I don't have any more on that specific worker. What I'm thinking here is that I would have 2 queues. RegularWorkQueue and SpecialWorkQueue. My SpecialWork workers would scale up to handle the SpecialWork and they would only subscribe to the SpecialWorkQueue. I'd like to have my other worker subscribe to the RegularWorkQueue and the SpecialWorkQueue, but always treat the RegularWorkQueue as more important than reading from the SpecialWorkQueue. Also, say 70-90% of the time the SpecialWork workers will be shut down completely. However, when they are up they are churning 24 hours a day for several days (usually). The RegularWork workers are always up, but any given day their utilization can fluctuate from 0 - 100% doing RegularWork only. The objective is that if I have 2 SpecialWorkers running 24 hours a day and a RegularWork worker is at 0% than I could take advantage of the fact that he is running idle and help out the SpecialWorkers finish that load of data faster. Even if he only processes a few messages of SpecialWork a day it can help a lot. Thoughts? Thanks, Adam On Tue, Jan 11, 2011 at 3:34 PM, Corey Kaylor <co...@kaylors.net> wrote: > If you need prioritized queues, then you may want to consider that in your > deployment. In other words, if it is more important to always process > message B's over other message A's... A queue is still a queue > http://www.lostechies.com/blogs/jimmy_bogard/archive/2010/11/18/queues-are-still-queues.aspx > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to rhino-tools-...@googlegroups.com. > To unsubscribe from this group, send email to > rhino-tools-dev+unsubscr...@googlegroups.com<rhino-tools-dev%2bunsubscr...@googlegroups.com> > . > 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 rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
