Corey, I see that pull request 6 (https://github.com/hibernating-rhinos/rhino- esb/pull/6) was never merged. I bring this up because I have two services running on the same machine both using a one way bus and am getting port conflicts. Pull six is too old to be usable as is so I was looking into how to solve this and have come up with two possible solutions:
1) Enable the user to configure a bus endpoint for a one-way bus (this is the approach that pull 6 seems to have taken) 2) Change RhinoQueuesOneWayBus not to use a hard coded null endpoint, but select one with an unused port and pass that to the RhinoQueuesTransport constructor. I prefer the latter solution because it doesn't require any explicit configuration of the bus port. Rather, its appropriate for tcp clients to auto select a port on their own from the 49152 - 65535 range. Or I could do both, giving people the maximum number of options. ;) Do you or any have a preference? -- 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.
