+1
Memcached's protocol maps so neatly to HTTP 1.1/WebDAV.
Randy
Sent from my iPhone
On Jul 7, 2007, at 9:11 PM, Paul Querna <[EMAIL PROTECTED]> wrote:
Paul Querna wrote:
Dustin Sallings wrote:
There'd be indexing overhead, but you could have an O(1)
invalidation if the tags themselves were versioned.
Assuming the cache time is short or you're accessing these
records,
cleanup should pretty much take care of itself.
Protocol-wise, would it make sense to have the tags be additional
tokens on the mutation line? i.e.:
<command name> <key> <flags> <exptime> <bytes> [<tag> [...]]\r\n
Well, it does bring up a wider issue of protocol versioning....
I was thinking about a more generic structure, if we ever did a
protocol
revamp, something like:
<command>\n
<meta>=<string||int>\n
data=<data>\m
END
So, for example a SET today would be like:
SET
key=foobar
flags=400
bytes=1000
data=...data...
And, thinking about that syntax a little more, we are just reinventing
HTTP, so, why not make memcached's protocol v2 just be HTTP :-) ?
-Paul
