Hi Miles,
It sounds rather strange that your mixing production and live environments together under the same system. From experience I would run them as separate systems (2 instances) which could be run on the same hardware if needed using a configuration transformation to set the queues up for each environment.
If you really need to have them mixed I would create 2 namespaces for the messages such as production and test and create an inherited message in those namespaces of each type. This means you can send each message off to its own dedicated queue as you were asking so you won't be mixing messages. The consumers can accept the base message type from memory so you won't need to duplicate consumers, but you will need to make sure the bootstrapper accepts the new message types.
Best regards,
Michael Lyons
--
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/4rOjNqOCLfgJ.
To post to this group, send email to rhino-t...@googlegroups.com.
To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.