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 On Sep 10, 2012 12:08 AM, "miles" <miles.wal...@gmail.com> wrote: > Hi, > > I am using RSB in a client where I want the user to be able to choose the > URI that they are communicating with for a particular message owner from a > list in the UI at runtime (basically they can switch between production and > test environments). Has anyone implemented anything like this, and what is > the best way to support this behaviour? I'm having trouble seeing how to > do this in a generic fashion... > > I'm thinking my approach should be as follows: > > - scan through the list of message owners for ones with endpoints > matching the one I want to change; > - for each message owner, get all the message types we are listening for; > - send an unsubscribe message for each message type to the old endpoint; > - change the endpoint via the endpoint router; > - for each message type that's subscribed, send a subscribe message to > the new endpoint; > > Using the API, is there a straightforward way to get to point 3? > > I'm assuming the endpoints aren't involved in any sagas, so there > shouldn't be any other considerations when unsubscribing - is that correct? > > Thanks for any assistance! > > Miles > > -- > 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-tools-dev@googlegroups.com. > To unsubscribe from this group, send email to > rhino-tools-dev+unsubscr...@googlegroups.com. > 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 rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
