protocol.coffee

Response types

Process the currently available input.

We're here because we're waiting for argc arguments to arrive before we can execute the next requet.

We're here because the length of the next argument is argl, and we're waiting to receive that many bytes.

We have sufficient input for one argument, extract it from the input and reset argl to await the next argument.

We have all the arguments we expect, run a command and reset argc/argv to await the next command.

See if we have more input to process.

We're here because we expect to read the argument length: $ CR LF

We're here because we epxect to read the number of arguments: * CR LF

Queue next command to execute (since we're pipelining, we wait for the previous command to complete and send its output first).

Invoke this command.

Send a reply back to the client and if there's another command in the queue, invoke it next.

Invoke next command in queue.

There's another command in the queue, add us at the end.

We're the next command in the queue, run now.

Send a response of the specified type.

Turns debugging on. To turn debugging off, pass 0 or false as the argument (no argument required to turn it off).

For testing purposes.

Resets the context. Discards current browser.

Returns the status code of the request for loading the window.

Tells browser to visit .

Tells browser to wait for all events to be processed.

Replies with error or OK.

Server-side of the Zombie protocol. See http://redis.io/topics/protocol

For each connection (stream): no delay, send data as soon as it's available.

Controlling

Start listening to incoming requests.

Returns true if connection is open and active.

Zombie.listen port, callback

Zombie.listen socket, callback

Zombie.listen callback

Ask Zombie to listen on the specified port for requests. The default port is 8091, or you can specify a socket name. The callback is invoked once Zombie is ready to accept new connections.