Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Apr 22, 2013
Commits on Apr 10, 2013
  1. Implementing the streaming response back to client

    authored
    Instead of using a redis client wrapped with the raw protocol, we now just use a simple tcp connection for handling request/response.
    There is one extra status check redis connection that is used to track the redis status and issue info/slave of etc commands
    
    This means
     * that Large responses are handled correctly
     * There is no conversion from one socket to another. Thus a performance boost esp for large responses.
     * Large number of events hooked up have been removed.
    
     There is still some cruft remaining with the read part of the protocol. Where a stream would help as well.
Commits on Apr 8, 2013
  1. Update to use new node-redis-raw api

    authored
    the new api wraps the redis object instead of the internal redis instance. Also the api allows us to keep updating the redis versions.
    And it works.
Commits on Apr 6, 2013
Commits on Mar 13, 2013
  1. Fixing issue with new redis startup being ignored.

    authored
    There was an issue in which after going down once the up notification
    would be ignored. So even though redis was up we'd detect that redis
    as still down.
Commits on Mar 12, 2013
  1. Updating the comment

    authored
Commits on Mar 11, 2013
Commits on Mar 6, 2013
  1. Updating benchmarks

    authored
  2. Now honouring log levels.

    authored
    Wrapped the winston logging so that we have a default log level set and
    a new instance is created everything log level changes, because looks
    like the old instance is being reused. This seems to give some big performance gains.
Commits on Jan 31, 2013
  1. Setting log level higher

    authored
Commits on Sep 17, 2012
  1. Fixes Path again

    authored
  2. Minor Documentation updates

    authored
  3. Adding configuration section

    authored
Commits on Sep 12, 2012
  1. Formatting readme.

    authored
  2. Closing connection if there is a end.

    authored
    This is a fix for #14, basically when there is a hard disconnect
    we don't have the peername, in such cases dont quit on the connection
    and let it die on it's own.
  3. Fixing a console.log

    authored
  4. Adding bind_address in the configuration.

    authored
    The older system hardcoded the bind to 127.0.0.1 and that meant users could
    only connect locally, adding the ability to specify a bind_address means
    users can choose a specific address to bind to if there are multiple ips available
    or 0.0.0.0 for all, or not specify any address which means it binds to 127.0.0.1
Commits on Aug 29, 2012
  1. Removing a console.log

    authored
  2. Semicolon

    authored
  3. Reads to Slave Bugfix. When no slaves are present.

    authored
    When there are no slaves, and the reads go to slave is set, then we would
    throw an exception, but this fix sends the read also to active so that
    it works consistently.
Commits on Aug 28, 2012
  1. Adding images

    authored
  2. Package version bump

    authored
  3. Formatting the readme correctly

    authored
  4. Do not crash after connection is closed.

    authored
    In cases where there is a connection timeout set in the redis.conf,
    we do not crash.
    
    Basically it has been handled by using the retry flag on the node-redis.
    we are also not hooking to the end event on the connection to track the
    server up/down status. This is as previously handled by the ping.
    
    There may also be problems if the ping timeout is set to a higher number
    than the connection timeout.
    
    We recommend using a ping timeout much lesser than redis connection timeout.
  5. Fixes to handle connections properly on read-write switches

    authored
    Simplified the connection pool handling when servers go up/down
    Support modes in config file to use reads goes to slavs or only to the server.
    Removed redundant files.
  6. Removing an irrelevant file

    authored
Something went wrong with that request. Please try again.