The implementation isn't going to change if it works - it's just that certain methods involving namespaces return unexpected results. For instance, grab_tail seems to be working incorrectly, pulling from the global LRU rather than the nested namespace LRU.
On Tue, Feb 16, 2010 at 7:01 PM, Nickolas Daskalou <[email protected]>wrote: > Thanks for that explanation Ikai. > > Since the details are still being worked out, should we not use the > namespace argument, in case its implementation suddenly changes? > > If it is indeed safe to use now (and the namespace argument actually does > "work" and is not just there as a placeholder), what is the data type? A > string? > > > > On 17 February 2010 08:57, Ikai L (Google) <[email protected]> wrote: > >> Nickolas, I thought the same thing when I first read about namespaces. As >> it turns out, namespaces with App Engine's memcache instance are not the >> same thing as prefixes. They are actual namespaces with their own LRU in >> addition to the global LRU. The details are still being worked out, though, >> but the idea is that you'll have features like constant time flushing of a >> namespace and nested namespaces, something you can't do with the >> distribution of Memcached that is available on the internet. This version of >> Memcache was necessary to ensure that users could not stomp on other users' >> memcache data. >> >> On Mon, Feb 15, 2010 at 8:11 PM, Nickolas Daskalou <[email protected]>wrote: >> >>> What's the difference between key_prefix and namespace when using the >>> Memcache.*_multi() functions? >>> >>> Maybe my understanding of namespace is wrong, but I thought namespace was >>> basically a (string) prefix on the cache key. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google App Engine" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<google-appengine%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >>> >> >> >> >> -- >> Ikai Lan >> Developer Programs Engineer, Google App Engine >> http://googleappengine.blogspot.com | http://twitter.com/app_engine >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-appengine%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
