Thanks Brian, that makes much more sense to me. I was concerned that
my queries were still being executed all the time to be dumped into
Memcached. I've got a basic class set up to handle my actual
implementation and thought perhaps I'd done something that caused the
query to be set each time
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 191 by romanenko.oleg: Implementation of CHECK command for
memcached
http://code.google.com/p/memcached/issues/detail?id=191
Hello.
I've been using memcached for storing data with a short lifetime and I
found that the
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 192 by stefan.b...@gmail.com: Crash when sending specially
crafted packet
http://code.google.com/p/memcached/issues/detail?id=192
What steps will reproduce the problem?
1. Start memcached in TCP mode. For example:
$
Comment #1 on issue 192 by romanenko.oleg: Crash when sending specially
crafted packet
http://code.google.com/p/memcached/issues/detail?id=192
it is easy to fix with small patch, but in memcached internals there are so
many functions without correct arguments cheking.
Attachments:
On Mar 15, 9:28 am, Oleg Romanenko romanenko.o...@gmail.com wrote:
Hello.
I've been using memcached for storing data with a short lifetime and I
found that the use of the add command to test the existence of a key
requires additional expenses, because if the key does not exist
already
