[erlang-questions] http client and server: inets, ibrowse, yaws
Thu Apr 5 16:17:06 CEST 2007
Thanks for all the advices.
Now I feel confident to use inets for http client.
For the server side, I just need to embed a very very simple http server. My
goal is to create an easy API to my application for any language. Thus I
will probably use yaws because it is easy to embed and it may enable a
future use of more sophisticated RPC (SOAP, JSON...). I would have used
inets httpd if I could have find an easy way to start it without external
On 4/5/07, Serge Aleynikov <> wrote:
> Ingela Anderton Andin wrote:
> >> Also I need to embed an simple HTTP server and got the same problem
> >> using 'yaws' or inets 'httpd'. Furthermore I cannot figure out how to
> >> httpd without config file or root directory ... yaws is simplest to
> > This one is harder to answer. The intes httpd and yaws have different
> > and both have their pros and cons. The Inets one is very old and
> inspired by apache. It also has a lot of legacy, that I would rather get rid
> of but that is impossible as we have customers that use it a lot. I think
> that yaws is also used a lot in the open source community and I can see
> things I like about it.
> > There is no officially supported way to start inets
> > without a config file, although webtool does that. I would not really
> recommend using webtools
> > strategy as it might change without warning. It's in the plans for inets
> to improve start
> > strategies but I am not making any promises until when this will be
> Being able to start inets by providing configuration options to the
> start function or from the application's environment in addition to the
> config file would definitely be a big plus.
> We've had quite a positive experience in using inets HTTP server. Not
> tried it for large sites, but we've successfully used it for internal
> AJAX client applications, extended it with custom modules, etc.
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions