I see the interface ICustomizeMessageHeaders, but only see it being used in Rhino Queues. What's the stance on supporting message headers ubiquitously throughout the framework? Ideally I'd like to be able to set arbitrary headers to be sent with a given message or batch of messages, regardless of whether I'm using MSMQ, Rhino Queues, etc... If it was a specific design decision to omit that functionality then what is the preferred solution for this? The scenario I'm up against is primarily that of having a sidecar for authorization/auditing information, and I'd really rather avoid restricting myself to a single base message class that contains the needed information or sprinkling it throughout all the message types using interface implementations or the like.
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.
