Cross-client memcached compatibility

Aaron Stone aaron at
Fri Feb 1 16:29:44 UTC 2008

On Fri, 2008-02-01 at 13:04 +0300, Tomash Brechko wrote:
> On Fri, Feb 01, 2008 at 01:30:20 -0800, dormando wrote:
> > simply to add another (standardized being a pre-req!) serialization 
> > flag, so the clients don't need to even think about launching a callback 
> I see what you are trying to achieve: with my proposal it's either
> native or common, with your both may coexist.  However, I'm more
> inclined to the solutions where the whole application agrees on one
> method, so native vs common should be mutually exclusive, and thus
> both may utilize the same hooks...

Correct, I prefer having two settings, "native" (which really only has
meaning to the client that sets the value) and "common" which indicates
some cross-language serialization method. Then we document that
serialization is as at-your-own-risk activity, and you'd better
configure it correctly on all clients or you're going to get garbage.

In particular, I'm thinking that some people may want to use features of
their languages that allow serialization of code and objects, not just
data, and so they'd need a way to continue to use the native
serialization of their language even though they might configure their
client to default serialize to some other format.


More information about the memcached mailing list