unlisten?

Any plans for bus.unlisten?

[mateodelnorte]

Haha. No worries. 😉 I still need to update the README, but here’s an outline of the changes as I sent to a client:

Send/Listen:

You can unlisten or destroyListener directly from an instance of a bus:

If you create a listener:

  bus.listen('my.event', { ack: true }, function (event) {
    count++;
    event.handle.ack();
  });

You can tell it to stop listening via:

  bus.unlisten('my.event');

One thing to note is that, due to how RabbitMQ works, you may get a few more messages after you make the call to unlisten(). You know when it’s officially stopped when RabbitMQ responds. Unlisten gives back an EventEmitter which will tell you exactly when that is via a ‘success’ event:

  bus.unlisten('my.event').on('success', function () {
      bus.send('my.event', { test: 'data'}); // this event won't be

picked up by any local listeners by the same routing key });

If you want to physically destroy the queue this listener is attached on, you can use destroyListener():

  bus.destroyListener('my.event.4');

It also returns an EventEmitter to show success:

  bus.destroyListener('my.event').on('success', function () {
        // the queue will have been physically destroyed at this time
  });

Publish/Subscribe:

Since you may have multiple subscriptions on a routing key in a process (though probably not a great idea to do so), it doesn’t make sense to unsubscribe directly from the bus instance. So, when subscribing, a subscription object is returned to you:

  var subscription = bus.subscribe('my.event', { ack: true }, function

(event) { // do something for your event here });

And to unsubscribe, you exercise the unsubscribe() method on that subscription:

  subscription.unsubscribe();

On Mon, May 12, 2014 at 11:50 AM, Chris Abrams [e-mail]:

Cool! I clearly did not accept the challenge 😮

— Reply to this email directly or view it on GitHubhttps://github.com/mateodelnorte/servicebus/issues/16#issuecomment-42849801 .

[chrisabrams]

Very nice! I like that you separated unlisten from destroyListener. This will be very helpful - I have a side project that I can now finish integration testing because of this 😃