sdwilsh / node-pulse Goto Github PK

It might be nicer to do something like this:

var consumer = pulse.createConsumer('bugzilla');

instead of:

var consumer = new pulse.BugzillaConsumer();

for various reasons, including that it'd be easier to conditionally create a different consumer and you might forget the new in front.

A better sample would be ideal so it's even easier to understand how to use this.

Since we now dispatch events, it'll be easy to add support for sending errors along to consumers too.

Request from @robarnold, but I'm hashing out the details. Debugging things is hard, and it'd be nice to be able to say something like connection.startRecording('filename') and then connection.stopRecording() to record a stream of events. Then you could just pulse.newRecordedConnection("filename", topics) and have the events streamed to you.

Not sure if we would want to delay the recording to be the same time or not. Does @LegNeato have any thoughts on this?

This isn't hard to do, but we don't currently have any way to close the connection to the server.

amqp can deal with this, it's just a matter of figuring out the right connection. There is no reason to create multiple connections to pulse, so we can be more efficient when a consumer creates multiple consumers with the same queue name.

Just need to figure out the right abstraction here...

[see later comments to see how this has been morphed]