> I don't know if this was inspired by the IRC discussion I was part of a few
> weeks ago or not, but that's awesome.  I've been wanting to see something
> like this for a while now and never had the time to attack it.  I look
> forward to trying it out very soon.

> Thanks!

> Jeremy

> 2010/12/28 Nicolas Favre-Félix <n.favrefe...@gmail.com>

>> Hello all,

>> After a discussion about HTTP interfaces to Redis on IRC, I have put
>> together a simple web server exposing Redis functions over HTTP:
>> https://github.com/nicolasff/webdis
>> Webdis is only a week old, and I'm not really sure what will come of it; I
>> would like this announcement to bring comments and suggestions for this
>> new
>> project, and I hope people will get interested.

>> The basic interface is the following: /COMMAND/arg0/arg1/.../argN,
>> returning a JSON object with the command as a key and Redis' response as a
>> value. A few examples:

>> $ curl http://127.0.0.1:7379/SET/hello/world
>> {"SET":[true,"OK"]}
>> $ curl http://127.0.0.1:7379/GET/hello
>> {"GET":"world"}
>> $ curl http://127.0.0.1:7379/PING
>> {"PING":[true,"PONG"]}

>> The raw Redis output is available by appending the query string
>> "?format=raw" to the command:
>> $ curl http://127.0.0.1:7379/LRANGE/x/0/-1?format=raw
>> *2
>> $3
>> abc
>> $3
>> def

>> So far, the following features have been implemented:

>>    - GET and POST commands.
>>    - JSON output by default, optional JSONP parameter.
>>    - Raw Redis 2.0 protocol output with ?format=raw
>>    - HTTP 1.1 pipelining (measured over 50,000 http requests per second on
>>    a desktop Linux machine with Apache Benchmark).
>>    - Connects to Redis using a TCP or UNIX socket.
>>    - Restricted commands by IP range (CIDR subnet + mask), returning 403
>>    errors for unauthorized clients.
>>    - Possible Redis authentication in the config file.

>> My main priorities are client-side timeouts and a working pub/sub system,
>> making it a Comet server using redis pub/sub channels. Adding support for
>> Web Sockets would be pretty cool too.
>> Webdis is pretty fast so far, thanks to the libevent HTTP implementation.

>> I look forward to seeing people play with it and I welcome all comments
>> and
>> suggestions; I'm having fun working on it.

>> Nicolas

>> --
>> You received this message because you are subscribed to the Google Groups
>> "Redis DB" group.
>> To post to this group, send email to redis-db@googlegroups.com.
>> To unsubscribe from this group, send email to
>> redis-db+unsubscribe@googlegroups.com<redis-db%2Bunsubscribe@googlegroups.c om>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/redis-db?hl=en.

> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.