How do you unit test your fuse files?
What if your IT department says "that worm that's putting 'f**ck USA
Government' all over web sites is a threat; we're setting our servers to use
start.cfm as the default filename; all index.cfm files must be renamed
immediately"?
What do you do when you want to change what happens after a user logs in?
Looks like you have to chase around the fuse files AND the xFATs to find out
how things work, then makes changes to the existing fuse file and its
associated xFAT.
Why even pretend that this approach is Fusebox? It violates the one tenet that
makes Fusebox what it is: all calls go back to the Fusebox.
I don't think I want to pay that price for search engine friendliness.
- Jeff
On 10 May 2001, at 14:21, Brad Roberts wrote:
> Check this out:
>
> In place of XFA's, I started creating what I call XFA Templates (or XFATs).
> I place them in the root directory. Here's a skinny XFAT example:
>
> <!--- SignUp.cfm --->
> <cfset attributes.fuseaction="members.signup.new">
> <cfinclude template="index.cfm">
> <!--- End --->
>
> Here's how I use it in my code:
>
> <a href="SignUp.cfm">Sign Up!</a>
> or
> <form action="SignUp.cfm">
>
> Opposed to: <a href="#request.self#?fuseaction=#attributes.xfa.signup#>Sign
> Up!</a>
>
> This is more "search engine friendly" and easier for people to read.
==============================================================
| Jeffrey S. Peters | "Specialization is for insects." |
| [EMAIL PROTECTED] | - Lazarus Long |
| PGP key for Jeffrey S. Peters at ldap://keyserver.pgp.com |
==============================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
