Permalink
Commits on Feb 4, 2011
  1. my actual nickname

    Scott Chacon committed Feb 4, 2011
  2. a little better

    Scott Chacon committed Feb 4, 2011
Commits on Feb 2, 2011
  1. @mojombo

    Release 1.2.4

    mojombo committed Feb 2, 2011
Commits on Feb 1, 2011
  1. @atmos
  2. @atmos
Commits on Oct 8, 2010
  1. @rtomayko

    Revert "avoid requiring rubygems"

    This reverts commit f50ba06.
    rtomayko committed Oct 8, 2010
  2. @rtomayko

    avoid requiring rubygems

    rtomayko committed Oct 8, 2010
  3. @rtomayko
Commits on Feb 23, 2010
  1. @mojombo
  2. @mojombo

    Version bump to 1.2.3

    mojombo committed Feb 23, 2010
Commits on Feb 22, 2010
  1. @rtomayko
  2. @rtomayko
  3. @rtomayko
Commits on Feb 19, 2010
  1. @mojombo
  2. @mojombo

    Version bump to 1.2.2

    mojombo committed Feb 19, 2010
  3. @mojombo

    poetry_mode--

    mojombo committed Feb 19, 2010
  4. @rtomayko
Commits on Feb 11, 2010
  1. @mojombo
  2. @mojombo

    Version bump to 1.2.1

    mojombo committed Feb 11, 2010
Commits on Feb 10, 2010
  1. @rtomayko

    don't trigger server error when client disconnects

    If the proxy client disconnects before the server connects or sends
    data, a proxy_connect_error or proxy_inactivity_error was fired
    because the client connection closes the server connection. This
    patch causes the server to check that the client is still available
    before assuming a connect/inactivity error.
    rtomayko committed Feb 10, 2010
Commits on Feb 9, 2010
  1. @mojombo
  2. @mojombo

    Version bump to 1.2.0

    mojombo committed Feb 9, 2010
  3. @rtomayko
  4. @rtomayko
Commits on Feb 6, 2010
  1. @rtomayko

    treat immediate disconnects like connect errors

    This can happen when there's some kind of load balancer or proxy
    between the proxymachine and the real server. The balancer accepts
    the connection and then immediately disconnects instead of rejecting
    the connection outright.
    rtomayko committed Feb 6, 2010
  2. @rtomayko
Commits on Feb 5, 2010
  1. @rtomayko
  2. @rtomayko
  3. @rtomayko
  4. @rtomayko
  5. @rtomayko
  6. @rtomayko

    remove futile connection timeout/retry code

    The removed try_server_connect logic will never fail because of
    EM's asynchronous nature. The ServerConnection.request, EM.connect,
    and proxy_incoming_to calls will always complete without exception
    because the actual socket operations don't take place until a future
    tick. In order to support connect failure detection and retries,
    we'll need to hook into the ServerConnection#connection_completed
    callback.
    rtomayko committed Feb 5, 2010
Commits on Nov 5, 2009
  1. @mojombo
  2. @mojombo

    Version bump to 1.1.0

    mojombo committed Nov 5, 2009
  3. @mojombo