memcache python API key collisionsFwd: key collisions

[Philip Neustrom]

I've never been able to reproduce this, and I haven't seen any test
code that reproduces it, either.  I'd be glad to fix this myself if I
knew what was going wrong here :/

>From what I understand, though, you're using the same memcache object
across multiple threads without considering what happens when multiple
clients step on each other's feet?

--Philip Neustrom

On 3/21/07, rkmr.em at gmail.com <rkmr.em at gmail.com> wrote:
> Hi
> Does any have a patch for this python memcached client api?
>
> "
> for (namely, as I understand it, cleaning up an existing connection when
> the application using it is terminated early), I would certainly review and
> "
>
> To solve this problem of key collisions.
> http://lists.danga.com/pipermail/memcached/2007-February/003605.html
> This is what the author or python memcache client api had to say.
> It will be great to have this patch.
> thanks a lot!
>
> ---------- Forwarded message ----------
> From: Sean Reifschneider <>
> Date: Mar 21, 2007 3:07 PM
> Subject: Re: memcache python API key collisionsFwd: key collisions
> To: "rkmr.em at gmail.com" <rkmr.em at gmail.com>
>
>
> On Wed, Mar 21, 2007 at 02:27:28PM -0700, rkmr.em at gmail.com wrote:
> >I hope your conference went great. Will you now have time to work on
> >the key collisions problem in python api for memcache?
>
> If someone can provide a patch to provide the functionality you are looking
> for (namely, as I understand it, cleaning up an existing connection when
> the application using it is terminated early), I would certainly review and
> include it.  However, it's not something I'm going to be able to resolve
> myself.  From what I can tell of the description, the problem is largely in
> your use of the client code (re-using an out-of-sync handle).  I just don't
> have time to develop and test a fix to this within the client code.
>
> Thanks,
> Sean
> --
>  This message is REALLY offensive, so I ROT-13d it TWICE.
>                 -- Sean Reifschneider being silly on #python, 2000
>