Yaws API discussion
Wed Jul 17 11:45:09 CEST 2002
On Wed, 2002-07-17 at 11:27, Mickael Remond wrote:
> Johan Blom <>:
> > So, my own humble opinion would be to have a closer look at the latest
> > inets version and help out with that. One of the main design goals with
> > inets is to have a fast "core" with only the most basic HTTP
> > functionality and then allow for extensions, provided by the module
> > design. Thus I assume e.g. a "yaws" extension should be quite easy to
> > implement.
> Why not. From what I remember from previous test with Inets 2.6 is that the
> performance was not as impressive as Yaws. But maybe we should work on Inet 3 to
> make it as fast with the same level of functionnality.
> Do you think it is something possible ?
Indeed. I see no reason why inets needs to be slower than e.g. yaws.
In fact inet_drv based HTTP parsing is already there. Next on my list is
a general overhaul of the EWSAPI interface and some internal
> We could then implement various templating approach as module (Yaws, ZPT, ...)
Yes, I believe so.
> If I remember right it was possible to considerably improve Inets performance by
> removing the log feature.
> This was very strange.
> Do you know if this is still the case ?
Don't know, we are not using it...
More information about the erlang-questions