My one reason for using url files: My rule in Fusebox development is that rank-
and-file coders never, no NEVER get to mess with index.cfm. I farm out the
coding by assigning modules to developers. As the architect, I can assign a
url file with a Fusedoc that says something like "I forward the user to the
National Geographic deep-sea exploration page". The developer gets to find the
URL for that resource and code it in the url file.
Sure, all the OMACs out there (One-Man App Creators, for those that haven't
seen my architecture musings) may think this approach is too picky and adds an
extra step of code. Fusebox is not a religion...
- Jeff
==============================================================
| 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