antirez

RESP3 specification

Versions history:

• 1.0, 2 May 2018, Initial draft to get community feedbacks.

Background

The Redis protocol has served us well in the past years, showing that, if carefully designed, a simple human readable protocol is not the bottleneck in the client server communication, and that the simplicity of the design is a major advantage in creating a healthy client libraries ecosystem.

Yet the Redis experience has shown that after about six years from its introduction (when it replaced the initial Redis protocol), the current RESP protocol could be improved, especially in order to make client implementations simpler and to support new features.

JulienPalard

#!/usr/bin/env python


def curry(func):
    """
    Decorator to curry a function, typical usage:

    >>> @curry
    ... def foo(a, b, c):
    ...    return a + b + c

robcowie

def test_root_output(client):
    resp = client.fetch('/')
    assert resp.code == 200
    assert resp.body == 'Hello, world'


def test_async_output(client):
    resp = client.fetch('/async')
    assert resp.code == 200

isaacs

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh