On Thu, Nov 10, 2011 at 11:25 AM, ionic drive <ionicdr...@gmail.com> wrote: > Yes Malcolm, > > thanks for the great and smart answer! > You are totally right, this was the reason why I was asking for, I > already knew their could be coming up new troubles. > > two more questions: > ------------------ > We don't have troubles with > 255 keys. as we do not have such long > keys. > But we have that issue: > 1) MemcachedKeyCharacterError: Control characters not allowed > > can't we just turn off caching for these two issues? > > I think the MD5 solution would work to fix both of them. > Why am I the only one who seems to be faced with such issues? > I thought millions out there do use memcached as their backend...? > Wouldn't be MD5 a great solution to all of us? The guys with small > sites, don't have issues with scaling, and the guys with big sites are > in the need of a stable memcached backend. >
Because md5 has a key size of 2^128 and memcached has a key size of (roughly) 128^250. Just stop generating keys with invalid characters in - ascii, no whitespace. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
