Hi Brian, Yep, these interaction were made between pylibmc and Memcached at localhost, 11211. I just skipped something that Dormando said, sorry, but he might have nailed it: "It might look mixed up if you're doing this over localhost and there's no lag. Try it over the internet or use a qdisc to add an artificial delay. It should line up more along the way you expect."
Cheers! __________________________ Diogo Baeder http://diogobaeder.com.br On Tue, Feb 19, 2013 at 12:08 AM, Brian Aker <br...@tangent.org> wrote: > Hi, > > On Feb 18, 2013, at 6:03 PM, Diogo Baeder <diogobae...@gmail.com> wrote: > > > I have no clue why libmemcached does that switch in the middle, but I > understood what you said about not expecting things to happen in an exact > order > > Are you sure the data is on the same server? Libmemcached responds back > with whatever returned first, which when spread across a number of > servers,... well who knows who might respond back the quickest. > > If you want order, then issue a single blocking get (one after another). > > Cheers, > -Brian -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
