I need to filter the subscriptions being picked up in the AutomaticallySubscribeConsumerMessages directly on the bus and would like to add something like IGatherMessages with the default being the AutomaticGatherer implementation. It'll follow same style of looping through any implementations of IGatherMessages and add to the collection for internal subscription. A few questions:
1. Are there objections to that? 2. Would you prefer me to just do an Unsubscribe() (clumsy) and leave the code alone? 3. If not, do I need to fork the master first and then issue a pull request or can I just do something from the clone of the master I am working on? Before you ask why the standard namespacing convention isn't enough, the answer is because I want to code the ConsumerOf interface in an assembly of handlers but have control over the actual implementation of the bus being used through configuration. Those Consumers will be in the container and therefore be automatically subscribed. I know the unsubscribe call would accomplish this, but it seems like it'd be handy to have something like the Bootstrapper offers with IsTypeAcceptableForThisBootStrapper directly on the bus. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
