Not to argue, because you make good points, but just about every shared host I've ever used gives you a mechanism for url rewrite. In fact most offer really well documented steps on how to do it too. I think it's probably equally as hard for a new dev to understand url rewriting as it is to understand how to set up a custom 404 handler and then a url parser based off of the cgi scoped vars etc etc. Further I think you'd find that Google will return many many more walk throughs on web server url rewriting vs coldfusion rewriting.
Six of one, half dozen of the other. I guess we'll just have to agree to disagree. On Tue, Sep 21, 2010 at 2:47 PM, Jacob Munson <yacoub...@gmail.com> wrote: > > > > > Sure it's personal preference I guess but I generally try to use the > right > > tool for the job. Data processing is best left to databases. URL > rewriting > > is best left to the server. And ColdFusion server can be left to serve > out > > ColdFusion pages. > > > > I won't disagree. I just think that there are cases where it makes sense > to > do URL rewriting in CF. And especially in this case, where we have a Flex > developer that is learning CF...maybe it's not the best idea for him to go > try to learn yet another technology when he can just use CF? Also, his app > might be on a shared host which would make using web server URL rewriting > difficult if not impossible. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:337278 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
