Absolutely, that was a primary design goal. There's really two packages at play here:
* Jeremy Shaw's web-routes provides some basic infrastructure.
* My web-routes-quasi provides the quasi-quoted syntax and template haskell code for generating the render, parse and dispatch functions.
Currently web-routes-quasi is pretty tailor-made for Yesod, but I'd be happy to make changes to have it fit your needs. I originally wanted the package to be more general, but realized I really needed user feedback on the features desired in order to do that properly.
Michael
On Tue, May 25, 2010 at 2:10 PM, Alberto G. Corona
<agocorona@gmail.com> wrote:
Could your web-routes be general enough to be integrated in other frameworks?. du to my special requirements I´m working on my own app-server (persistence, clustering, state, threading, but not web framework) and I would like to have web components available to put at the top, rather than web frameworks.
Alberto
2010/5/24 Gregory Collins
<greg@gregorycollins.net>
Michael Snoyman <
michael@snoyman.com> writes:
> This monologue isn't meant as a Yesod-is-better-than-Snap, it's meant
> to point out that type-safe URLs are a very powerful feature, and I
> think it fits very nicely with the Haskell nature. I'd really urge
> people to look hard at them and consider using them.
Enough people want this that I've been talking with Jeremy about doing a
web-routes backend for Snap -- sounds like less than an hour's work. On
the todo list...
G
--