Inets HTTP client stability
Fri Oct 28 13:46:05 CEST 2005
If you looking for passing http requests from one end to another,
why not use a pure tcp based solution, you can still inspect the
data and headers. I can't see any real reason to parse the protocol
pass it through the system then assemble it again.
The reason i suggest yaws is that it is known to handle high volumes.
I been doing some work with inets and from my point of view it is
a messy beast.
On Fri, 28 Oct 2005, Heinrich Venter wrote:
>> I would probably opt at yaws/ibrowse or a simple gen_tcp.
> Why not the standard inets httpd/http?
> I will not be serving actual web pages. Instead it will only be used
> for http based protocols. Yaws seems a bit of overkill for something
> like this.
More information about the erlang-questions