Mailing-List: contact erlang-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: erlang@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPNuaCjSp4ZbzLj2rmVfyfqAMuipnjevH9AGgWR6vkm2nO-z+w@mail.gmail.com>
References: 
 <CAPNuaCjSp4ZbzLj2rmVfyfqAMuipnjevH9AGgWR6vkm2nO-z+w@mail.gmail.com>
Date: Thu, 7 Nov 2013 19:14:22 +0000
Message-ID: 
 <CABvT1DG79n-SOSRgbLLa+x0pY+bxg+AUPhVfT3xUjuDQJ=+f-Q@mail.gmail.com>
Subject: Re: Parsing json request body into usable object
From: Robert Newson <rnewson@apache.org>
To: erlang@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Please stop opening more identical threads if you don't get an immediate answer.

The native view server is not documented, it's not much more than an
afterthought. It has no sandbox (map functions can read/write/delete
any file the user it runs as can, open network sockets, etc).

B.


On 7 November 2013 16:55, Stanley Iriele <siriele2x3@gmail.com> wrote:
> I am trying to rewrite a lot of my JavaScript code in Erlang and I'm
> hitting a few weird spots
>
> Maybe this is a dumb question... In an update handler or a list
> function....or whatever.... How do you parse incoming request bodies into
> binary Erlang objects or proplists... In these functions?... I'm not seeing
> anywhere in the docs where this is made clear