Hey Dave, Dave Gray wrote: > What do you gain by doing it this way instead of using mod_rewrite or > similar? Obviously mod_rewrite isn't as flexible in that you need to > update your ruleset separately instead of only changing your > application level code, but that seems like an acceptable tradeoff to > me.
1. I like my apps to be able to fully run standalone with the integrated server. Things I load off to the actual webserver (static files, for example) would just shortcut certain requests. 2. Every 'list' endpoint has its own private action path. Therefor it can easily be used with uri_for and I can change the URI layout of the application (even via the configuration file) without having to touch links, redirects and the like. Of course, if the application shouldn't _run_ on those URIs, but just redirect to something else, mod_rewrite might be the way to go. To me it is more a question if it's an application-level or deployment-level decision. .phaylon _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
