I would definitely stay away from that java port if I were you, unless it's been updated recently. The whole reason for us writing the BeITMemcached client in the first place was that we were using the java port, but it would suddenly start throwing lots and lots of errors. When we tried to understand how it worked so we could fix it, we realized that it was a very sloppy least-effort port of a java client, and that it would be much less work to write a good .Net client from scratch instead.
/Henrik On Wed, Feb 10, 2010 at 23:57, Perry Krug <[email protected]> wrote: > I've been in touch with the Enyim developer directly, sounds like he's > still actively engaged with the project even if there haven't been any major > updates as of late. > > There's also a client maintained within Sourceforge: > http://sourceforge.net/projects/memcacheddotnet/ > > > On Wed, Feb 10, 2010 at 2:54 PM, Jozef Sevcik <[email protected]> wrote: > >> Enyim, but I'm not sure about noreply. >> http://enyimmemcached.codeplex.com/ >> However, there seems to be last commit from Dec 2008 >> >> On 10 February 2010 23:37, Jeremy Dunck <[email protected]> wrote: >> >>> I'm looking for a .Net client that's actively maintained, preferably >>> with noreply support. >>> >>> This one looks to be maintained: http://code.google.com/p/beitmemcached/ >>> >>> Did I miss any others? >>> >>> BeITmemcached doesn't seem to support noreply. >>> >>> Thanks! >>> >> >> >
