Before diving in too deep let's first find out if this is actually necessary. With my background in NServiceBus I automatically felt naked without header support when starting my last project with RSB, but now looking back at it, I'm thankful that I had to make that information explicit within my contracts. Made a lot of things much easier to do and it's crystal clear for another developer to see what's going on. I'd say unless there is a burning need to add this I'd say let's skip it - keep RSB small, sleek, and opinionated. If the message headers are specific to Rhino Queues only then that gets moved there as a feature of the Rhino Queues RSB integration only. Thoughts?
On Fri, Feb 4, 2011 at 8:55 AM, Corey Kaylor <[email protected]> wrote: > This looks ugly, might take a bit for me to change this and maintain > backwards compatibility. Starting to look into it now. Seems like a better > long term solution is to abstract the individual transport's formats and > handle it for all types with one shot. Not sure I've got the stomach or the > time at the moment, but we'll see when I dive in a bit deeper. > > -- > 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. > -- 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.
