<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Re: Cross-client memcached compatibility</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>How about standardising on something like json? Either that or we're basically going to have to put a custom serialization rules together each client has to follow?<BR>
<BR>
<BR>
-----------------------------------<BR>
This message was sent by Blackberry<BR>
<BR>
----- Original Message -----<BR>
From: memcached-bounces@lists.danga.com <memcached-bounces@lists.danga.com><BR>
To: dormando <dormando@rydia.net><BR>
Cc: memcached@lists.danga.com <memcached@lists.danga.com><BR>
Sent: Wed Jan 30 06:08:47 2008<BR>
Subject: Re: Cross-client memcached compatibility<BR>
<BR>
<BR>
On Jan 29, 2008, at 21:40, dormando wrote:<BR>
<BR>
> Wonder if we can just put up a list of flag recommendations (and <BR>
> storage mediums?) and see if it catches on? Or perhaps pisses <BR>
> someone off enough to provoke discussion?<BR>
<BR>
<BR>
Makes sense to me.<BR>
<BR>
The most controversial part would be lists and dictionaries since <BR>
they nest types.<BR>
<BR>
--<BR>
Dustin Sallings<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>