!
__
Diogo Baeder
http://diogobaeder.com.br
On Tue, Feb 19, 2013 at 8:00 PM, Brian Aker br...@tangent.org wrote:
Agreed, I'll take a look and see why that is happening.
From looking at the code I can see where it is happening, I just need to
find out if there was a reason for it. The default value
Hi guys,
I'm getting a rather strange behaviour when I try to issue a get-multi on
memcached, so I'm not sure this is a problem with my understanding of how
the protocol was specified or if it's an issue with either pylibmc or
libmemcached.
What I expect:
As I understand it, for multi-get,
Hi Dormando,
So, I've tested Memcached by sending direct byte blocks to it in the order
I expected it to behave, and indeed it works, as you said it would:
https://gist.github.com/diogobaeder/4982425
I have no clue why libmemcached does that switch in the middle, but I
understood what you
Yep, agreed, Dormando, not a problem, just different from my initial
expectations. I'll just have to figure out how to use Tornado in my favor,
to build this part, and deal correctly with the asynchronicity. :-)
Cheers!
__
Diogo Baeder
http://diogobaeder.com.br
On Tue
something else that is failing to me that I didn't yet notice. In
other words, libmemcached seems to play just fine with ordered batches.
Not sure if this adds anything here, but I thought you might want to know.
:-)
Cheers!
__
Diogo Baeder
http://diogobaeder.com.br
On Tue
