Queues set via mapper proxy do not match settings declared via cluster

ezmobius / nanite

self assembling fabric of ruby daemons

Apache License 2.0

735 stars 64 forks source link

Queues set via mapper proxy do not match settings declared via cluster #30

Closed akeem closed 13 years ago

akeem commented 13 years ago

I came across an issue where the queues set by the mapper proxy did not match those set by the cluster. I changed their declaration to ensure that they now durable as well. Specs for the mapper proxy were updated to ensure that 'push' and 'request' use queues with appropriate settings.

There are some additional changes to my fork that can be ignored if most users are not using RSpec2

akeem commented 13 years ago

eh, that is not a pretty pull request. The following commits are relevant, not sure why it wouldn't only capture items from the latest merge onward.

45f7db3e89d0c1e37854b913967bf302b1640477 3b9b39d7f82848f9bf3d52b55b9be77a9a380fa7 4e7f8185276073aaa39f7f4ebdcbc231426f863a

roidrage commented 13 years ago

I'm actually just gonna merge the ones dealing with the mapper proxy. Other than that, I'm not going to merge anything new into the current master, instead into the 0.5 (currently mapper_rework) branch. So if you want to see the other patches go into that release, be sure to rebase against that.

akeem commented 13 years ago

cool, I will start making changes to the newer branch