Documentation

Everything is allright.

Heartbeat, reply with the NOP Command.

Server has closed the connection.

The server sent back an error.

A message to be processed. The values are: Nanosecond Timestamp, number of attempts, Message Id, and the content of the message to be processed.

Catch-all message for future expansion. This currently includes the reply from Identify if feature negotiation is set.

The protocol version

No-op, usually used in reply to a Heartbeat request from the server.

Client Identification + possible features negotiation.

Subscribe to a specified 'Topic'/'Channel', use True if its an ephemeral channel.

Publish a message to the specified Topic.

Publish multiple messages to a specified Topic.

Update RDY state (ready to recieve messages). Number of message you can process at once.

Finish a message.

Re-queue a message (failure to process), Timeout is in milliseconds.

Reset the timeout for an in-flight message.

Cleanly close the connection to the NSQ daemon.

Catch-all command for future expansion/custom commands.

Response to a Command from the server.

An error in response to a Command.

Messages.

For future extension for handling new Frame Types.

Something went wrong with the command (IDENTIFY, SUB, PUB, MPUB, RDY, FIN, REQ, TOUCH, CLS)

Bad Body (IDENTIFY, MPUB)

Bad Topic (most likely used disallowed characters) (SUB, PUB, MPUB)

Bad channel (Like BadTopic probably used an disallowed character) (SUB)

Bad Message (PUB, MPUB)

Publishing a message failed (PUB)

Same as PubFailed (MPUB)

Finish failed (Probably already finished or non-existant message-id) (FIN)

Requeue failed (REQ)

Touch failed (TOUCH)

New unknown type of error (ANY)