I name them consumers. You can pass a bootstrapper type to the host, and the bootstrapper can override a method (configure container, iirc) to do the selection
On Thu, Jan 29, 2009 at 4:15 PM, Matt Burton <[email protected]> wrote: > > Quick question - I'm looking at the RSB host service and I'm wondering > what the prescribed strategy is here for usage. What I've been doing > up to this point in my spikes is using the remote app domain host with > bootstrappers that implement the "IsTypeAcceptableForThisBootStrapper" > method to filter based on the namespace I'm interested in for that > particular host. This allows me to keep all my services in a single > assembly, filtered by namespace. The host doesn't give this level of > control, however, and seems to want a single assembly that will in > turn contain a single bootstrapper class. I definitely prefer to have > as few assemblies as possible. Would it be possible to add namespace > filtering as an argument or something along those lines to the host? > Or am I missing something altogether here? > > Also - in NSB there's the concept of message "handlers" - > IMessageHandler<T> - in RSB we have ConsumerOf<T> - do you typically > name your classes as consumers - "...Consumer" or are they handlers - > "...Handler"? I know it's a minor point but someone was asking about > it... > > Thanks, > Matt > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
