[erlang-questions] Re: Web server structure: Rack
Mon Jan 11 14:11:47 CET 2010
On Mon, Jan 11, 2010 at 4:10 AM, Ciprian Dorin, Craciun <
> On Mon, Jan 11, 2010 at 9:53 AM, Dmitrii Dimandt <>
> > - You can't reliably write generic code that will run across all Erlang
> web servers, since every web server differs in how it presents information
> to your code and what it expects from your code
> > - Because of that you can't reliably abstract parts of your functionality
> (caching, setting etags etc., see e.g.
> http://rack.rubyforge.org/doc/Rack.html) into truly reusable pieces of
> > Because of that a common web server interface is actually a blessing
> and, in my opinion, should be accepted more aggressively.
> Indeed such a <<common web server interface>> could be a
> <<blessing>> for the enterprise world, where you need something stable
> and reliable. But there is also a drawback: I remember (maybe I'm
> wrong because I'm not a web developer, but I've kept a close eye),
> that a few years ago (5 maybe?) the only usable (as in enterprise
> ready) web server was Apache (now we have LigHTTPD, Nginx, and of
> course Apache, thus not too much better in terms of diversity)...
> What I'm trying to say: a <<common web server interface [...] that
> should be accepted more aggressively>> leads to (framework) lock-in...
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
You guys might want to take a look at ewgi (Erlang web gateway interface),
that aims to make it possible to have the same interface in front of all
So far it is supported with Yaws, Mochiweb and inets.
More information about the erlang-questions