After having wasted many hours with pecularities of Rails and then Merb (which is definitely far better than Rails, IMO), I discovered the joys of Rack. It's sufficiently low level but not too down and dirty and is a joy to program with. So, Ewgi + Yaws would definitely be a welcome development. 
I'm going to read up the spec but I'd presume it lets us wrap 'middleware' erlang modules in an onion structure (much like Rack) to provide more functionality?
On Sun, Jul 19, 2009 at 4:01 PM, Dmitrii Dimandt <> wrote:
Are there any plans to make Yaws ewgi-compatible?

ewgi's author plans to take a shot at creating a patch for Yaws and Mochiweb to make them natively compatible with ewgi. What's the community's stance on this?

For those who don't know what ewgi is:

ewgi is Erlang's answer to Python's wsgi,, and Ruby's Rack,

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, and ewgi example middleware,

ewgi's authors would like to see ewgi spec,, 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:

There's at least one web-framework that is currently ewgi-compatible (the one I'm collaborating on, Compatibility with ewgi may lead to a larger expanse and adoption of web-frameworkks

Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at:
Erlyaws-list mailing list