Using Rhino-ESB such that we have 1 publisher that publishes a FileUploaded message 1 consumer that subscribes to the FileUploaded message and calls a remote webserivce. 1 consumer that subscribes to the FileUploaded message and does long running CPU intensive work.
All the above are in separate processes. If 10 messages are published in quick succession I cant really have more that 1 instance of the CPU intensive consumer running at any one time, but am happy for multiple calls to the remote webservices. Doe Rhino ESB have built in functionlaity to help me with this scenario, or should I consume the event adding it to a queue of sorts, and have a background thread process the queue. I suspose I am looking for a message/a...@readthreadcount type of configuration.
-- 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.
