Share

.NET memcached client library

Code

Programming Languages: C#

License: GNU Library or Lesser General Public License (LGPL)

Repositories

browse code, statistics, last commit on 2007-06-07 svn co https://memcacheddotnet.svn.sourceforge.net/svnroot/memcacheddotnet memcacheddotnet

Show:

What's happening?

  • Comment: Make memcached client mockable..

    eburley@ittoolbox.com - forgot to include my email address.

    2008-06-18 18:35:50 UTC by nobody

  • Make memcached client mockable..

    MemcachedClient is currently a sealed class, and doesn't implement any interfaces. This kills the ability to unit test classes that depend on memcached independently of memcached. Suggest either making MemcachedClient unsealed, with mockable virtual methods, or (my preference) extracting an interface for mockery.

    2008-06-18 18:34:11 UTC by nobody

  • Comment: Nullreference in unittest

    I further examined the error and with logging I got the following: System.IO.IOException: Could not connect for 50 milliseconds bij Memcached.ClientLibrary.SockIO.GetSocket(String host, Int32 port, Int32 timeout) in C:\Projects\DotNet\Memcached\Memcacheddotnet\trunk\clientlib\src\clientlib\SockIO.cs:regel 163 bij Memcached.ClientLibrary.SockIO..ctor(SockIOPool pool, String host, Int32...

    2007-08-09 17:01:11 UTC by ezbee

  • Nullreference in unittest

    I have altered Unittests.cs to use nunit(version 2.4.1). When i run a local memcache version (win32 1.2.0) and when I repeat the unittest serveral times i get a nullreference in test1 and sometimes in test11. When i run memcached with -vv i do not see a store action in the debug log. So either there is a problem with expiration of with the socket because no connection is made. I am using...

    2007-08-09 12:41:00 UTC by ezbee

  • Comment: version number increment

    Update AssemblyInfo with the following: [assembly: AssemblyVersion("1.1.*")]. Then every official rebuild will increment. Or change it to 1.1.5.* and change the build number manually for each release.

    2007-06-25 10:38:08 UTC by carpdeus

  • clientlib 1.1.5 released

    (from the changelog) 7 June 2007 (TG) -Bugfix. Applied a patch from a contributer (thanks Dave Peckham!) that fixes a bug where we don't get the proper size of the buffer. In many cases the code would still work fine, but you may have experienced periodic errors when working with very large objects, or seeing wasted...

    2007-06-07 15:45:19 UTC by timiscool999

  • .NET memcached client library

    timiscool999 committed revision 20 to the .NET memcached client library SVN repository, changing 1 files.

    2007-06-07 15:40:03 UTC by timiscool999

  • .NET memcached client library

    timiscool999 committed revision 19 to the .NET memcached client library SVN repository, changing 5 files.

    2007-06-07 15:36:06 UTC by timiscool999

  • Comment: client sends overly large size in "set" command

    After more thinking on this, I have a better solution. GetBuffer() is efficient in terms of memory usage--ToArray() creates a copy. But we can fix this better on the SockIO class. If we overload Write(byte[] bytes) to Write(byte[] bytes, int offset, int count) then the method can pass the correct (read "used") length of the buffer on to the network stream: public void Write(byte[] bytes) {.

    2007-03-29 04:40:45 UTC by dpeckham

  • client sends overly large size in "set" command

    Because the memcached client uses the MemoryStream's GetBuffer() method instead of the ToArray() method, the client sends more bytes than necessary to the server. A serialized 1000 byte array is 1028 bytes long. So, the server should send the command:

    2007-03-26 17:33:37 UTC by dpeckham

Our Numbers