You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.
Module python-memcached uses memcache ability to add meta-data (flags) to store type of data, and uses it for parsing.
For example it sets flags=0x1 to say that data is pickled and should be unpickled.
Kestrel silently drops flags so meta-data is lost which leads us to unexpected behavior: we write python tuple "(1000, 100)", we get "(I1000
I100
tp1
." as a result.
As far as I understand Kestrel code, to achieve this functionality we should:
add .flags member to QItem
move instantiation of QItem from PersistentQueue.add to KestrelHandler.set
use item.flags in formatting response in KestrelHandler.get
If these are acceptable changes I'm going to code them and present patch for review shortly.
The text was updated successfully, but these errors were encountered:
that sounds fine to me. you will also need to add a new variant of ADD in the journal -- maybe ADD_FLAGS. and just always write ADD_FLAGS but still be able to read ADD and ADDX.
Module python-memcached uses memcache ability to add meta-data (flags) to store type of data, and uses it for parsing.
For example it sets flags=0x1 to say that data is pickled and should be unpickled.
Kestrel silently drops flags so meta-data is lost which leads us to unexpected behavior: we write python tuple "(1000, 100)", we get "(I1000
I100
tp1
." as a result.
As far as I understand Kestrel code, to achieve this functionality we should:
If these are acceptable changes I'm going to code them and present patch for review shortly.
The text was updated successfully, but these errors were encountered: