v0.4.1

Bug fixes:

• #17 - Client now closes even when there is no active IPC connection

v0.4.0

0.4.0

v0.3.0

Deprecations

• [Server] Event: 'closed' Deprecated in favor of more familiar close event. Scheduled for removal in v1.0
• [Client] Event: 'closed' Deprecated in favor of more familiar close event. Scheduled for removal in v1.0

Bug Fixes

• Event: 'closed' was documented for Server but never emitted (#7)

v0.2.0

Breaking Changes:

• clientId is now treated a string instead of an int. (It is still a number, but this is an implementation detail which should not be relied upon).
• connectionClose Server event has been dropped (listen to exposed socket instead)
• close event(s) are now closed to distinguish from the close event many core I/O elements use.

New:

• A custom transcoder can now be provided. This allows for specialized encoded/decoded of messages when
  JSON just won't do. (#1)
• Added Example for high-throughput/noisy client implementation.

Enhancements:

• Greatly expanded docs -- especially the API docs (always more work to do here!)
• More specific errors in some send failure cases
• Clarified event api
• Improved handling of abrupt disconnects. What can't be handled is now documented.
• Underlying net.Socket is now exposed to give applications direct access to socket events when
  they matter.

More NPM package detail

Functionally equivalent to v0.1.1 -- simply adds more metadata to the npm package

Initial Release

Provides the minimum feature set

• Ability to send files from server to client and vice versa
• Ability to target a specific client or broadcast to all clients from the server
• messages are "heard" using events driven by Nodes' native event loop.
• Client resilience (connection auto-retry, auto-reconnect)