title: Why use MEMCACHED_BEHAVIOR_NOREPLY?
body: <p>I am writing a library that wraps libmemcached.</p>
  
  <p>I noticed that there is an interesting behaviour setting for memcached which says that I can indicate that I do not care about the results of my memcached commands...</p>
  
  <p>It is known as MEMCACHED_BEHAVIOR_NOREPLY. Why would somebody want to use this?</p>
  
  <p>It would be great if someone could point out a few use cases? multi-get / multi-set spring to mind, but I am not clear how this would be useful.</p>