Armagan Amcalar

Not by default, but you can put a unique id into your requests and then `requester.sock.queue.filter` according to that.

@mikield no, it's only a routing prioritization based on response times.

Sorry to come in late to the discussion. @claustres you have summed it up quite well — that's the current scenario. I believe centralizing discovery per node as @aikar suggested...

Exactly, we’d love to implement TLS — however no one has gone to the length to implement it. If you’d consider contributing, you’d be welcome.

Looks interesting! Some lines seem redundant, but if you can make it work within cote, we can merge it and release as a newer version of @dashersw/axon.

Sorry, didn’t see your previous message. Axon is probably dead at this point, so I would assume not.

It should be the same as the actual handler, and it should have a means to stop execution, either through a `next()` function or throwing inside a promise.

@tericnexus cool! do you have it on a fork? does it work with callbacks as well? (because cote has to support callbacks for now.)

This would be a great feature. In fact, cote already has an undocumented feature called `subset`s. If you look at `requester.js` code, you'll see that messages can be routed to...

Hi! In fact there was a pull request earlier to streamline this — #27. However we weren't satisfied with the API and stopped working on it. I'd love to help...