no reply patch

Brian Aker brian at
Tue Feb 5 22:23:37 UTC 2008


On Feb 4, 2008, at 11:15 PM, Tomash Brechko wrote:

> 'noreply' nothing will be send, so I avoid this message too.  Also,
> not seeing the result actually stresses the fast that with 'noreply'
> you can't be sure of the command outcome ;).

How about making the debug message say "noreply" in it so that the  
person debugging the code knows that a message occurred, but that it  
will not be sent?

verbose mode I use to debug problems. I want it extended :)

Much easier to ask an end  user to run -vv then have them learn gdb  
when trying to find a problem.

> Indeed, the 'more' keyword I mentioned in other mail may be used in
> this place, as it is mutually exclusive with 'noreply'.

I need to go back through my notes, I know I have had a couple of  
ideas where "wow... if I had this change...". A flexible keyword would  
be handy for this.


Brian "Krow" Aker, brian at
Seattle, Washington                     <-- Me                <-- Software    <-- Fun
You can't grep a dead tree.

More information about the memcached mailing list