I would like to announce that I've pushed the latest changes to
Beepbeep which make it the first (?) publicly available web-framework
to support ewgi.
See this version's changes:
http://github.com/dmitriid/beepbeep/commit/b27ac8a359968d1dbf67e7d17d...
and docs:
http://beepbeep.dmitriid.com/documentation/middleware/
What's ewgi you ask?
ewgi is Erlang's answer to Python's wsgi, http://www.python.org/dev/peps/pep-0333/
, and Ruby's Rack, http://rack.rubyforge.org/
It is a minimal interface between the webserver and you app. It lets
you applicaton to be completely server-agnostic. More importantly, it
allows chainable middleware. See Django's middleware, http://docs.djangoproject.com/en/dev/topics/http/middleware/
and ewgi example middleware, http://github.com/skarab/ewgi_examples
ewgi's authors would like to see ewgi spec, http://code.google.com/p/ewgi/wiki/EWGISpecification
, to become EEP in the future. However, there are not too many people
talking about ewgi for some odd reason. Even though it's already being
used in production: http://smarkets.files.wordpress.com/2009/07/huntermorris-erlangfactor...
________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org
