Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of
 sebastiancohnen@googlemail.com designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=REf6OEWboxtyxw1tz1I7MzeBu1RVj4PSlPBZEoyMi/rKAQPqpA3MPDWbgeAFh/lY8T
         wGorlULrfEH/v+8lfpb5BTakG8737eOUIxRSyIA5YDhex8EwqUNkm6iosLOAY0kXr0CT
         miSnGePjAO4+MP1xqnYk9uoHWx50B7ooIS7TI=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: arguments for couchdb - binary data output ?
From: Sebastian Cohnen <sebastiancohnen@googlemail.com>
In-Reply-To: <4BED13B2.1020104@digitalgott.de>
Date: Fri, 14 May 2010 12:42:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2F8DAA8-A79B-4604-91C8-8445D4EEB2C3@googlemail.com>
References: <AANLkTimb6aZ0PY75tUYoOB1tVcooFfHwjXuQMCDjvHkt@mail.gmail.com>
 <4FD426D8-F807-4FCE-8B98-36B9B0B2C058@googlemail.com>
 <4BEBCDAB.4070708@digitalgott.de>
 <AANLkTikgHoM8publkQ1wWxMaJksZ_0OIEe43cZgFS63W@mail.gmail.com>
 <20100513160136.GB9782@seblaptop> <4BEC2A4C.4090303@digitalgott.de>
 <2C9F0F2E-F87B-4BC7-B55D-7D7A2E965428@googlemail.com>
 <4BEC43B3.8070807@digitalgott.de>
 <5625AF56-BC6C-4C4E-A675-1D47711C97B9@googlemail.com>
 <02D23147-0128-454A-87BF-169CDE6D35CF@gmail.com>
 <4BEC4F33.7060503@digitalgott.de>
 <C4D26E40-B531-440F-BDE0-2AD880D02C7D@gmail.com>
 <4BEC5694.2050205@digitalgott.de>
 <3041A366-8876-4C76-89E2-981863C9A3FA@gmail.com>
 <4BEC5E21.4020604@digitalgott.de>
 <73395B99-69DC-4812-A6C2-58A98B7A6D44@gmail.com>
 <4BED13B2.1020104@digitalgott.de>
To: user@couchdb.apache.org

please start new threads when posting to the ML


but back to topic: I'm not sure what you want to know/hear. In terms of =
efficiency, sure, binary is much more "transport"-efficient then =
json/text. But json on the other hand is a perfect fit for web-centric =
application (json is a subset of javascript e.g.)...

=09
On 14.05.2010, at 11:11, c.Kleinhuis wrote:

> Hello,
>=20
> one more question is, how is json output comparable to direct binary =
output, in my eyes
> the json is the compactest human readable transfer format, and the =
difference json<->binary
> is far less than compared to xml<->binary
>=20
> what do you think ?
>=20
>=20
> thx
> ck
>=20