v0.1.6

• Disconnection now removes nodes from internal store - they should no longer be found by .connectTo() calls on their ID.
• Changes to disconnect events so that they only fire ONCE per connection.
• Channels can now call conductor.rejct(id, reason) to reject a connection in progress.
• Removal of unnecessary debugger keyword when setting event handlers.
• connectTo() calls will now timeout - defaults to never, but can be user configured to reject after a given time.

v0.1.5

• Added "onclose" event, which responds to EXPLICIT REQUESTS TO CLOSE THE CONNECTION. If you want a riskier metric (which will catch failures but may report false positives), then use "ondisconnect".
• Added "ondatachannel" event to tracked connection objects, this should fire when a data channel is added to a connection - in particular, when a received connection becomes ready for use.
• Added "ondisconnect" event to tracked connection objects, this should fire when a connection to another client terminates (either deliberately or on browser/node exit).
• Successive calls to .connectTo() will return the promise that was supplied on the first count.

v0.1.4

• Fixes #4, where configs did not correctly merge. This allows serverside applications to work as intended now.
• Fixes #2, #3. These bugs both resulted from incorrect handling of resources and promises.

v0.1.3

• Addition of simple .close() method on connections. This closes a connection for real, and is not intelligently managed.

v0.1.2

Change of dependencies to get webrtc-adapter-test from the official git now that API changes have been merged.

v0.1.1

• Removal of wrtc as an optional dependency.

v0.1.0

• Addition of .renameConnection() method for channels to use in cases where the destination is not yet known.
• Addition of .onconnection property, called when a channel is opened to the current user from another source.