Thanks for all the advices.<br><br>Now I feel confident to use inets for http client.<br><br>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 config file.
<br><br>Thanks everybody!<br><br><div><span class="gmail_quote">On 4/5/07, <b class="gmail_sendername">Serge Aleynikov</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ingela Anderton Andin wrote:<br>>> Also I need to embed an simple HTTP server and got the same problem with<br>>> using 'yaws' or inets 'httpd'. Furthermore I cannot figure out how to start<br>
>> httpd without config file or root directory ... yaws is simplest to embed.<br>><br>><br>> This one is harder to answer. The intes httpd and yaws have different approaches<br>> 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.
<br>><br>> There is no officially supported way to start inets<br>> without a config file, although webtool does that. I would not really recommend using webtools<br>> strategy as it might change without warning. It's in the plans for inets to improve start
<br>> strategies but I am not making any promises until when this will be ready.<br><br>Being able to start inets by providing configuration options to the<br>start function or from the application's environment in addition to the
<br>config file would definitely be a big plus.<br><br>We've had quite a positive experience in using inets HTTP server. Not<br>tried it for large sites, but we've successfully used it for internal<br>AJAX client applications, extended it with custom modules, etc.
<br><br>Serge<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:email@example.com">firstname.lastname@example.org</a><br><a href="http://www.erlang.org/mailman/listinfo/erlang-questions">