[erlang-questions] Erlang Web Libraries & Frameworks

[Jesse Gumm]

Hi,

While, for the most part, you're right about Nitrogen not being
*aimed* at simple restful api development, it's not too hard to do.

wf:q and wf:qs will read values from querystring and post variables,
so you can easily pass around json and what not.

Using a template is optional, since every page's entry point is the
main() function.

Further, if you'd rather not do querystrings, you can trivially do
path parsing. IE: assuming you have a module called 'api', for the
path /api/myinfo/123, wf:path_info() returns "myinfo/123".

Between those and mochijson, building a simple api should be a breeze
in nitrogen.

-Jesse

On Tue, Aug 9, 2011 at 6:04 PM, Sam Elliott <sam@REDACTED> wrote:
> Hi erlang-questions,
>
> Recently I needed to compare a few Erlang web libraries and frameworks
> for a friend who was writing a simple internal API endpoint. He
> suggested I should publish the rundown for others, and I thought I'd
> also circulate it here. I'm relatively new to Erlang, so I have
> probably missed a few libraries.
>
> I'll try to keep it updated as people send me information, so don't
> hesitate to contact me if i've got something wrong.
>
> The article: http://lenary.co.uk/erlang/2011/08/erlang-web-libraries/
>
> What are your thoughts?
>
> Sam
>
> --
> Sam Elliott
> sam@REDACTED
> --
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>



-- 
Jesse Gumm
Sigma Star Systems
414.940.4866
gumm@REDACTED
http://www.sigma-star.com