GithubHelp home page GithubHelp logo

Comments (7)

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024
The support for expire time has been removed in delete. See
http://github.com/dustin/memcached/tree/rewritten-bin/doc/protocol.txt 

Then both delete commands should return "ERROR\r\n" ?
Or maybe a more appropriate return message would be "CLIENT_ERROR <error>\r\n" 
for both?

Original comment by [email protected] on 4 Dec 2008 at 12:19

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024
It's unclear to me what the remaining bug is here.  If there's still a bug 
here, can
we update the summary so that we know what it is?

(acknowledging there's confusion around the disappearance of delete with 
timeout)

Original comment by [email protected] on 22 Jan 2009 at 1:21

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024
I think the only change under 2) should be returning "CLIENT_ERROR <error>\r\n"
instead of just "ERROR\r\n". Just because it's a more appropriate error message 
in
this case. I'm not sure about 1). We could keep it the way it is - i.e. 
accepting the
expire time in the delete command even if this means accepting a wrongly 
formatted
command. Maybe that's ok because of backward compatibility issues.

Original comment by [email protected] on 22 Jan 2009 at 8:19

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024
I've pushed a branch for this (finally... this is an old one).

Original comment by [email protected] on 29 Oct 2009 at 6:09

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024

Original comment by [email protected] on 29 Oct 2009 at 6:09

  • Changed state: Started

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024
1) stats-detail and udp test fails
2) I liked that you wrote a better error message, but could you change it to:
"CLIENT_ERROR bad command line format. Usage: delete <key> [noreply]"

This would let the user know how to send the command without having to open the
protocol spec... ("bad command line format" could be replaced with "Syntax 
error" if
you want to shorten the error message ;-))

Original comment by [email protected] on 29 Oct 2009 at 1:01

from memcached.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 19, 2024

Original comment by [email protected] on 29 Oct 2009 at 5:14

  • Changed state: Fixed

from memcached.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.