Thanks, added it to the code.google.com wiki/FAQ. http://code.google.com/p/memcached/wiki/FAQ
On Dec 13, 12:47 pm, "Aaron Stone" <[email protected]> wrote: > On Fri, Dec 5, 2008 at 10:10 PM, Dustin <[email protected]> wrote: > > > On Dec 5, 8:21 pm, ionous <[email protected]> wrote: > >> i poked around on the faq and mail lists, but haven't seen anything > >> definitive; > >> does anyone know whether there is a guaranteed order to the items > >> returned in get_multi? > > > You may observe some pattern to the results, but non is guaranteed. > > Ooh, let's document that! > > >> if i asked for the values at keys: 5,4,3,2,1 - and key 1 expired > >> itself - > >> would memcached return the keys: 5,4,3,2 in that order? > > >> i playing with a stack-like ( queue-like? :) idea that uses auto- > >> expiring values to detect the current bottom of the stack -- it's a > >> minor thing but it would simplify the logic in my code that process > >> the results of get_multi if the order of the returns happened to be > >> the order of the requests. > > >> ( i'm using the python client which returns the keys as dictionaries, > >> so i'd have to change that code to return a list, but really i'm just > >> curious about the server's mechanics ) > > >> thanks for any insights! > > >> -simon.
