Hey, that gives me an interesting thought:
A variation on Fusebox: Have the Application.cfm store the "desired URL" in a
variable, but always go to the root index.cfm. The root index.cfm will look at the
"desired URL" for the action to be performed and dispatch it accordingly. This style
would give you nice URLs to hand out, and would be VERY search engine friendly and
STAT program friendly.
At 11:01 AM 4/6/01 +0100, Maddison, David wrote:
>Check out the Application.cfm file of Fusebox-X. It automatically reroutes
>the user to the root index.cfm file, (called the dispatcher in Fusebox-X),
>and also puts the circuit the user was trying to get to on the end of the
>URL. So basically you can hit a sub circuit, and the application.cfm file
>will re-route you to the same circuit, but through the dispatcher.
>
>The current one re-routes using the Fusebox-X syntax, but you can easily
>modify it! Also comes in handy so that you don't have to give out XFB
>URL's. In Fusebox-X we use the fact that everything is routed through the
>dispatcher, to inject services such as security automatically into the call!
>
>Check it out www.wildfusion.com/fuseboxXdocs. Announcement on Fusebox-X
>comming later today (GMT)....
>
> << David Maddison >>
> wildfusion
>
>W: http://www.wildfusion.com
>E: [EMAIL PROTECTED]
>YahooIM: maddisondavid
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
