Scenario 1: -> request comes to IIS/Apache -> URL gets rewritten -> ColdFusion gets request and deals with as normal
Scenario 2: -> request comes to IIS/Apache -> URL gets rewritten -> ColdFusion gets request -> Some code parses url to extract variables -> request carries on as normal I know which I prefer. Scenario 1 has less code to go wrong, less code to maintain, less code to run. Scenario 2 adds no clear benefits IMO. Dominic On 7 October 2011 18:58, Michael Grant <[email protected]> wrote: > > Why would there be any additional code than what the OP already has to > handle the current implementation? > > > On Fri, Oct 7, 2011 at 1:45 PM, Wil Genovese <[email protected]> wrote: > >> >> Because you will still have to write CF code to translate the URL in params >> whereas doing the rewrite to tradition url params makes the values available >> in the URL scope with no extra code. >> >> >> Wil Genovese >> Sr. Web Application Developer/ >> Systems Administrator >> CF Webtools >> www.cfwebtools.com >> >> [email protected] >> www.trunkful.com >> >> On Oct 7, 2011, at 12:36 PM, Michael Grant wrote: >> >> > >> >> >> >> I would be weary of rewriting a pretty url to another pretty url. >> >> >> > >> > Why? >> > >> > >> > >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348021 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
