You are viewing a plain text version of this content. The canonical link for it is here.
Posted to erlang@couchdb.apache.org by Stanley Iriele <si...@gmail.com> on 2013/11/07 17:55:09 UTC
Parsing json request body into usable object
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
Re: Parsing json request body into usable object
Posted by Stanley Iriele <si...@gmail.com>.
Ahh. Apologies... When I posted I realized I hadn't gone through the
subscription process completely so I thought it just ignored my posts
On Nov 7, 2013 11:14 AM, "Robert Newson" <rn...@apache.org> wrote:
> 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 <si...@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
>
Re: Parsing json request body into usable object
Posted by Robert Newson <rn...@apache.org>.
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 <si...@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