Ah, awesome. Yeah, I noticed the key stuff wasn't in protocol/commands, which is why I went digging in the first place. Good point on with the distribution though, I was staring at the document in the repo without thinking, "this obviously _comes_ with memcached."
- Marc On Tue, Feb 8, 2011 at 10:13 AM, dormando <dorma...@rydia.net> wrote: > protocol.txt also comes with the software... so technically it's > memcached.org -> tarball -> spend 1.75 seconds doing `ls` > > Or typing "memcached key" into google gets you enough results. > > Or wiki -> protocol/commands (two clicks!) though the key stuff should be > repeated at the top there (just fixed that). Probably should be repeated > somewhere else too, which we'll improve next time. > > On Tue, 8 Feb 2011, Marc Bollinger wrote: > > > I understand why the 'official' protocol.txt is where it is, but to > get there from memcached.org, you go from > > memcached.org -> code.google.com -> github > > > > which just seems kind of janky. > > > > - Marc > > > > On Tue, Feb 8, 2011 at 9:55 AM, dormando <dorma...@rydia.net> wrote: > > > Where do I find the invalid characters for a memcached key? > > > > Buried in the wiki somewhere + protocol.txt. > > > > in short, for ascii; no spaces or newlines. > > > > > > > > > > > -- Marc Bollinger mbollin...@gmail.com
