Well I got it working more or less for msmq (needed lots of tweaking). Can't seem to get this working for RQ because of the ports issue. Coming up with a process level singleton that deterministically assigns a port number to an endpoint is not as fun as it sounds.
I think I would need to implement Corey's idea of one RQ instance per machine (just like msmq). Looking at the RQ code, it looks like rhino.queues://localhost:2200/a and rhino.queues://localhost:2200/b should work (c/d?). The only snag is that RhinoQueuesTransport creates a new QueueManager when it starts. Trying to think of what would be the simplest thing here... we could throw IQueueManager behind wcf using a named pipe, and install as a windows service. But I know that ayende has a special place in his heart for WCF so that may not be the way to go. Thoughts? On Fri, Feb 25, 2011 at 6:07 PM, Corey Kaylor <co...@kaylors.net> wrote: > Nice! > > 2011/2/25 João Bragança <joao.p...@braganca.name> >> >> Example project up at >> >> https://github.com/JoaoBraganca/rhino-esb-topshelf >> >> TODO: >> Support rhino queues (hard to do since IIRC each queue needs to be on >> its own port) >> Build script >> Readme.md >> >> >> On Fri, Feb 4, 2011 at 9:01 AM, Corey Kaylor <co...@kaylors.net> wrote: >> > A conventional approach or DSL with MSMQ might not be too hard. Rhino >> > Queues >> > in its current form might not be as easy. I've kind of felt for a while >> > that >> > Rhino Queues would be better deployed on its own where processes on the >> > machine can communicate through a channel of some sort. This would also >> > make >> > an Administrative UI much easier to build in isolation also. >> > >> > -- >> > 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. >> > >> >> -- >> 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. >> > > -- > 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. > -- 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.
