…the queue don't match on both sides, agent queues are set as durable when created but not in the mapper when handling pings, set this option.
The 1.8 version doesn't allow the declaration of an exchange with different parameters anymore. See "Exchange equivalence" at: http://lists.rabbitmq.com/pipermail/rabbitmq-announce/2010-June/000025.html This makes the simpleagent example work again.
Useful if you want to specify e.g. timeouts.
… of an error.
…ent graceful shutdown would fail when it hasn't work through any messages yet. Conflicts: lib/nanite.rb
…nstead using the proper ones as specified by the protocol. Fixed some broken specs too.
…ils because of arbitrary reasons.
…ious version wrapped results in Nanite::Result object leading to inconsistent behavior
…f exit hooks. That way even though an agent still has jobs to finish, a new instance can be started using the same identifier, taking over new work.
…dumped to the log file.
…A lot more reliable, but requires calls to done to include the deliverable handed into the actor method as second parameter.
… It'll wait until all running jobs are finished, but disconnect from all queues before that, so it's safe to bring up a new agent in its place. Due to the asynchronous nature of the agents it's not safe to assume that their finished when the method returns, because users may (and should) use EventMachine in their exposed methods. So finished jobs must be explicitly declared as such using the method done.