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 bchesneau@gmail.com
 designates 72.14.220.153 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=owJSzxLcr2YLsNHexwiFRf9RpLWHwyfHrWQ4UkdW3XcHQ2unQHZQuf8GQ+MGblvMK7
         PrFHnesp6AnGuRRG2/WumFt1VoYMpuk0R2Io8EnuCPGDL9mTwuQGJfY6Cf4Yt0AKxsKi
         Aytz1/24XnPpB+lH5RNwIgHYCVkSH/McdFq4k=
MIME-Version: 1.0
In-Reply-To: <4AA0631C.5070702@borwankar.com>
References: <4AA05FD3.6000905@borwankar.com>
	 <e2111bbb0909031738n6816c3fdy74d8646ea1d062be@mail.gmail.com>
	 <4AA0631C.5070702@borwankar.com>
Date: Fri, 4 Sep 2009 14:12:53 +0200
Message-ID: <b7cd8ed10909040512t2678ebd4k8e03021d8f7ae11f@mail.gmail.com>
Subject: Re: e4x, xml and json
From: Benoit Chesneau <bchesneau@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 4, 2009 at 2:45 AM, Nitin Borwankar<nitin@borwankar.com> wrote:
> Paul Davis wrote:
>>>
>>> If an xml document is imported into couchdb via built in e4x support in
>>> spidermonkey then
>>>
>>
>> I don't understand how you would import a document via e4x when that
>> doesn't exist on the front side of CouchDB.
>>
>> Paul
>>
>
> Ahh! stupid question. =A0Misunderstanding of where e4x fits.
> As I see it now - blindingly obvious (thanks Paul) - no XML api on the wa=
y
> in.
>
> OK, so I will need to convert XML to JSON before saving to Couch and then
> query via views to emit JSON
> ( I don't want to emit XML anyway ).
>
> Thanks much,
> And allow me to retreat back to the middle of the forest,
>
> Nitin
>

You could eventually fit a doc with xml via _update I guess.

- beno=EEt