I have (clumsily) fixing an issue in rsb where it currently simply looks at the first message in batch being Published for its subscription info. I am publishing a number of messages that may or may not be subscribed to (these are events from a store) and which are subscribed to at different endpoints. Under the current setup (PublishInternal), if a message doesn't happen to be subscribed to in the same endpoint the first message in the batch it will not get sent to get handled.
The initial fix is to GetSubscriptions for each message in the batch to make sure all subscriptions have been harvested that are interested. My question is about the performance of something like this on a massive batch of messages where I am iterating on the collection (please see my pull request). This scenario doesn't seem far fetched to me, but if there is a better way of implementing it I'd like to hear 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 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.