First release.
- Single connections (
Connection
Objects) are stable. - Clustering is functional, but not well exercised or particularly robust.
- NO TESTS FOR YOU! (Soup Nazi says: "Needs tests!")
Small improvement to Connection
API: publish
method now accepts topic
strings:
client.publish(*topic*, message, callback)
- Major overhaul of the
Protocol
state machine- TCP failure tolerance and reconnection
- Proper transaction handling for REQ/REP Commands (
IDENTIFY
,SUB
,PUB
,CLS
) - Error response handling
- Separation of the
Connection
controller fromNSQClient
. An instance ofNSQClient
now stores connection data for a singlensqd
endpoint and provides methods to create/access a dedicated publisherConnection
and to create subscriberConnection
s. Subscriber
state-machine- Wrap and manage the ready-state of subscriber
Connection
- Handle re-subscription on re-connection of the underlying
Protocol
- Handle clean un-subscription on close of the underlying
Connection
- Wrap and manage the ready-state of subscriber
- Use int64-native to handle message timestamps