michael at snoyman.com
Mon Apr 12 11:05:27 EDT 2010
On Mon, Apr 12, 2010 at 1:44 AM, Alberto G. Corona <agocorona at gmail.com>wrote:
> Hi Michael,
> I´m involved in the development of an application server (not a framework)
> with rather different goals than Yessod (its´nt so elegant). I will tell
> more about it whenever there is something solid enough to play with it.
> Just a few questions to clarify my mind:
> When you mention WAI you mean Web Access Initiative? I checked your
> Network.WAI package and it seems that gzip facilities and so on have nothing
> in common with usability and accesibility issues.
> No, it stands for Web Application Interface. It's a standardized interface
between web applications and web servers, so you can write an application
once and have it run on multiple backends, eg CGI, FastCGI, stand-alone
> - Could you point me to documentation about web-routes? I´m in the internet
> business since a few years, so I suspect that I know this with another name.
> Thank you a lot.
> web-routes is not yet released; the code is available at
http://src.seereason.com/web-routes/. I believe Jeremy will be releasing it
in the not-too-distant future, and there will be more documentation
available then. I also just wrote a blog entry that tangentially
> 2010/4/3 Michael Snoyman <michael at snoyman.com>
>> web-routes-quasi is now at the point where it can be used for sites, and
>> I'd love to hear some feedback. I've put together a little sample that
>> demonstrates how you can use quasi-quoting and define your routes, embed
>> subsites and serve the resulting application via WAI. (My example uses WAI,
>> but the package itself is not tied to WAI.)
>> The code is on github; the main function for the blog is in blog.hs
>> (with the lowercase b). I believe this just depends on Jeremy's web-routes
>> package, wai and wai-extra.
>> Note that I did not use web-routes-wai; I think there are some problems in
>> there for breaking up the pathinfo, and I didn't have time to dig through
>> it. Also, this package currently ignores entirely the defaultPage component
>> of Site, though if there is desire support can be added for it.
>> One minor bug is that you can't have an alternate GET, POST, PUT or DELETE
>> constructor imported; hopefully that will get cleaned up.
>> Any comments and suggestions are welcome! My goal is to port Yesod over to
>> this as soon as the web-routes set of packages are released, so if you're
>> interested in Yesod, you should be interested in this too ;).
>>  http://github.com/snoyberg/web-routes-quasi
>> web-devel mailing list
>> web-devel at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the web-devel