I'm maintaining that one, although since it just works fine there hasn't been much to do with it lately. I should get around to implementing the binary protocol sometime, but so far I haven't had the time or the need to do so, and the lack of a proper windows version of the server makes it even less pressing.
What would you need noreply for? When I read through the protocol specs it seemed a kind of flaky feature that would be hard to implement right in the client. If you're concerned about the performance of having to wait for a reply you're not interested in, you could try moving all your bulk sets to the built-in .Net threadpool instead, that should give you approximately the same results. I've thought about doing a parallell multi-set, but for the bulk version where you don't care about results, I'd rather implement it using the quiet binary commands than the ascii noreply command. /Henrik On Wed, Feb 10, 2010 at 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! >
