Werl (Wsgi for ERLang) like the magical Smerl
Wack like Rack which is a clean Ruby WSGI:

http://rack.rubyforge.org/



On Nov 12, 3:31 pm, Roberto Saccon <[EMAIL PROTECTED]> wrote:
> Name suggestions: erlwgate, gaterl, werlgate, uniweb, erlywebunify or
> a greek god as fantasy name.
>
> Roberto
>
> On Nov 12, 7:09 pm, Filippo Pacini <[EMAIL PROTECTED]> wrote:
>
> > I've only used yaws for now and gave a quick look to mochiweb and
> > iserve, but I'd like to test one of the two sooner or later.
>
> > For the interface following python's wsgi implementation we can think at
> > it as having two sides: the "server" or "gateway" side and the
> > "framework" one.
> > The framework side is a module providing a fun (e.g. handle_req)
> > accepting an environment record (basically a wrapper around the http
> > request and containing also data specific for the framework) and a
> > callback from the "gateway" side to send the response to the server.
> > The server/gateway for every http request it translates the request data
> > from the server format to the environment format and invokes the
> > application fun.
>
> > I should already have some code written. I'll try to improve it, test at
> > least with mochiweb and yaws and put it online somewhere.
> > Suggestions for a name? erlwsgi seems quite ugly.
>
> > filippo
>
> > Roberto Saccon wrote:
> > > I actually started long time ago to make erlyweb work with iserve, but
> > > never got to a point where it actually worked.
> > > Anyway, erlyweb on mochiweb would rock, and a common gateway interface
> > > even more !
>
> > > Filippo, do you have a concrete suggestion for such a gateway
> > > interface ?
>
> > > For using mochiweb to replace yaws you need to be aware that mochiweb
> > > is not a webserver (you have to build one from scratch using
> > > mochiweb) and does not offer anything for static file serving, so you
> > > need either to rely purely on a CDN, or another webserver (Lighttpd or
> > > nginx) or add static fileserving and ETAG  handling to mochiweb.
>
> > > regards
> > > Roberto
>
> > >> Hi,
> > >> at the moment we have at least four different erlang web servers (yaws,
> > >> mochiweb, inets_httpd and iserve). IMHO it would be a good idea having a
> > >> little gateway interface like python's 
> > >> wsgi:http://www.python.org/dev/peps/pep-0333/
>
> > >> This would allow easily building frameworks and libraries abstracting
> > >> from the underlying server. You write frameworks and libraries using the
> > >> gateway interface without worrying whether you are working with yaws,
> > >> mochiweb or whatever.
>
> > >> I've been thinking about this for a while but hadn't have much time to
> > >> work on it yet.
> > >> What do you think?
>
> > >> cheers,
> > >> filippo
>
> > >> Yariv Sadan wrote:
> > >>> Now there's definitely a good reason to remove the dependency on the
> > >>> Yaws arg. It shouldn't be too hard -- I think the only internal
> > >>> dependency is where ErlyWeb inspects the appmod to derive the
> > >>> requested component. If anyone wishes to use ErlyWeb with MochiWeb, it
> > >>> would be great it they took on this little project and contributed
> > >>> their work. (I've already started using Yaws for Vimagi, so I don't
> > >>> want to go through the trouble of switching, but MochiWeb does look
> > >>> like a great alternative for new apps.)
> > >>> On Nov 11, 2007 10:15 PM, Robin <[EMAIL PROTECTED]> wrote:
> > >>>> MochiWeb was recently open sourced:
> > >>>> Announcement:
> > >>>>http://bob.pythonmac.org/archives/2007/11/07/mochiweb-another-faster-...
> > >>>> Google Code:
> > >>>>http://code.google.com/p/mochiweb/
> > >>>> Google Group:
> > >>>>http://groups.google.com/group/mochiweb
> > >>>> ErlyMochiWeb anyone?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to