Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jul 9, 2007
  1. Merging 1.4 to default.

  2. merged 1.3 into default

  3. merged pipeline into default

  4. merged 1.2 into default

  5. Merged 1.1 into default.

  6. Merged 1.0 into default.

Commits on Jul 8, 2007
  1. Semi-functional client based on NodeLocator.

    	The way to handle bulk gets in the event of a failing node is unclear, so
    the failing node test currently fails.
Commits on Jul 7, 2007
Commits on Jul 5, 2007
  1. Pulled QueueAttachment out into MemcachedNode.

    	QueueAttachment was a nested class in MemcachedConnection that was used to
    hold per-connection information.  It was called QueueAttachment because it was
    attached to the select queue or something like that.  MemcachedNode seems like
    a better name, and it's going to need to be exposed some as we get into more
    pluggable node selection algorithms.
Commits on Jul 4, 2007
Commits on Jun 29, 2007
  1. Fix a warning in a test.

    	I just upgraded to eclipse 3.3 and it's finding warnings and errors that
    should've been found before, but weren't.
  2. Some changes to get this bench thing to run under the profiler.

    	There were a couple of stupidities in how the client was set up, and some
    issues keeping large numbers of async sets down.  It still doesn't model a real
    application very well, but may be good enough at showing what would happen in a
    peak situation.
  3. Support for working around a failing server.

    	Apparently, the common thing to do is check the status of a server when
    performing a command against it, and trying the next server in the list when
    the server is unavailable.
    	My previous behavior was to queue a command against a server regardless of
    its status such that when a server was available the command would be processed
    as close to immediately as contention would allow, but when a server was
    unavailable, the command would wait around for the server to come back up.
    	The new behavior is something near the middle of this.  When a server is
    unavailable, I'll try the next server in the list.  I repeat until I've
    exhausted every known server and then just queue it for the one to which it
    belonged in the first place.
Commits on May 22, 2007
Commits on May 18, 2007
Commits on May 17, 2007
  1. Some documentation updates.

Commits on May 16, 2007
Commits on May 4, 2007
  1. Updated version to 1.3.1.

Commits on May 3, 2007
  1. Turn some assertions into harsh logging.

    	I had some conditions where these assertions were firing due to
    cancellation when a server went bad.
Commits on Apr 24, 2007
Something went wrong with that request. Please try again.