Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.215.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ_m3YAm7AkJv7ao0DH5oiciYAvD0a6vD=VPmR3RSwP7veBfCg@mail.gmail.com>
References: 
 <CABn9xAGK0WbPhpkbxyKQo9N1KEsm=rx81V7FVDaRGPjXjncvWQ@mail.gmail.com>
	<CAJNb-9qaqqJmB0AG8dUmq1H5eijoejBMf2EZjChYtd+FK9RNfA@mail.gmail.com>
	<CAAL6JQjGmRNnUQ6xO72Nu82-p8ZLwb4srVUVaViB8tAw8XLb2A@mail.gmail.com>
	<CABn9xAFO7Ypsg5ZjzZ-rk5b4dK75fNjjz4-XqnM7ThifEf6PHw@mail.gmail.com>
	<CAJ_m3YAm7AkJv7ao0DH5oiciYAvD0a6vD=VPmR3RSwP7veBfCg@mail.gmail.com>
Date: Tue, 4 Oct 2011 22:08:30 +0200
Message-ID: 
 <CAJNb-9q-3OTGj5SHWBkYK9P=fsEDC8256n7AYKEqxAhVUtrgyQ@mail.gmail.com>
Subject: Re: Universal Binary JSON in CouchDB
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 4, 2011 at 9:33 PM, Paul Davis <paul.joseph.davis@gmail.com> wr=
ote:
> For a first step I'd prefer to see a patch that makes the HTTP
> responses choose a content type based on accept headers. Once we see
> what that looks like and how/if it changes performance then *maybe* we
> can start talking about on disk formats. Changing how we store things
> on disk is a fairly high impact change that we'll need to consider
> carefully.

+1
>
> That said, the ubjson spec is starting to look reasonable and capable
> to be an alternative content-type produced by CouchDB. If someone were
> to write a patch I'd review it quite enthusiastically.
>
>

I think I would prefer to use protobuffs format though. Anyway if wwe
change the api to handle all types that would be pluggable without
problem.

- beno=EEt