> I've gone even further in a developing app and use URLs like:
>
> http://www.MyApp.com/HL/LL/OA/OO/index.cfm/IN.845/CD.50022/CN.3711
> 5146/HD.475000/AL.B/LL.E/OR.5260.HTM
>
> where I parse the "/" delimited list to obtain the value of
> several passed
> parameters (the value of OR is 5260, for example). I use the folder
> sequence "/HL/LL/OA/OO/" to define a "Breadcrumb Trail" that allows users
> to "one-click" to ANY earlier page in the user's current path.
Great stuff. We've gone one step further (sideways?) and eliminated the need
for the index.cfm reference (thereby avoiding the NT4/SP6 url parsing
problem). Just set up a custom 404 error handler in IIS properties that goes
to a CF URL... that "notfound.cfm" page can do all your parsing, and you
could have nice URLs like:
http://mydomain.com/usa/california/oakland/dentists
...or whatever, all being processed by just one template (fusebox works
great) and no directories behind it. Only issue with this is that you need
to point all form actions to a real page, since the IIS redirect will lose
the form variables.
Ron Allen Hornbaker
President/CTO
Humankind Systems, Inc.
http://humankindsystems.com
mailto:[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
