WSGI. I don’t want an apache replacement, or at least have to bootstrap one just to write a webapp. I’d much rather have something very simple and callback based to handle requests and output dynamic data (and push static data through something else. No offense to erlang on that score but …)
Erlang wish list
This entry was written by David Terrell and posted on August 13, 2007 at 3:05 pm and filed under erlang, tech. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Both comments and trackbacks are currently closed.
3 Comments
While not wsgi, there is a fcgi binding at http://code.google.com/p/efcgi/ thats very easy to connect to apache or whatever frontend you may prefer.
Also, the erlang socket driver has built in fcgi framing if you want to roll your own (fcgi packets are very easy to parse with erlang’s binary matching)
That’s true. What I’m hoping for is a standard way of factoring out the differences between efcgi, httpd, pico or anything else, and just have a simple API that handles web requests that anyone can implement to and deploy in different scenarios.
Was just reading your mmap question on erlang mailing list (but don’t have an answer) and somehow landed here. Are you still looking for such a webserver ? I found it. Bob Ippolito’s Mochiweb, see link and details at my blog