<!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>Lol is it me or did we start this thread a bit like this? :)<BR>
<BR>
Just in case my vote hasn't been picked up I'm a +1 for json becoming a standard formatting too. have we got an flag spare across all the common clients?<BR>
<BR>
Cheers,<BR>
Kieran<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: Ciaran <ciaranj@gmail.com><BR>
Cc: memcached@lists.danga.com <memcached@lists.danga.com><BR>
Sent: Mon Feb 11 21:20:39 2008<BR>
Subject: Re: Cross-client memcached compatibility<BR>
<BR>
Ciaran wrote:<BR>
> JSON sure seems popular with a lot of people ;) In fact so far I've had<BR>
> +4 for JSON and no other suggestions ;)<BR>
> - Ciaran<BR>
<BR>
It is widespread and language independent. It is basically javascript<BR>
syntax. So, it is standard. Many languages like PHP have native<BR>
support for making JSON strings and parsing them.<BR>
<BR>
--<BR>
<BR>
Brian Moon<BR>
Senior Developer/Engineer<BR>
------------------------------<BR>
When you care enough to spend the very least.<BR>
<A HREF="http://dealnews.com/">http://dealnews.com/</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>