Although, large CFM files can cause a problem with the CF Server. Having to
parse huge CFM files can crash it (but only *really* big ones).
Phil
>===== Original Message From "Matthew J. Vecera" <[EMAIL PROTECTED]>
=====
>It's tough to find a valid argument "against" fusebox, particularly since
>fusebox is a "suggestion". (Perhaps it is slowly becoming a "religion".)
>
>Rather than an "argument against" - here is another option to consider:
>
>Fusebox does seem to get a bit choppy for some people. You may find
>yourself with a lot more cfm files than you anticipated. Granted, it is
>the most organized bunch of files you've ever administered - but it's a
>bunch of files.
>
>The "Every Page is an Island" philosophy does address this. EPIAI, as far
>as I know, is NOT fleshed out as well as Fusebox - it's just an idea where
>every one CFM file is a self contained application in one huge
>CFSWITCH. It may sound like Fusebox, but the CFSWITCH contains long-code,
>not CFINCLUDEs.
>
>In other words, if you made a ROLODEX-type app., ROLODEX.CFM would contain
>the code to view/sort/add/edit/delete contact information. All forms and
>links would submit them selves back to ROLODEX.CFM with a variable
>indicating the CFCASE and execute the appropriate code.
>
>Sound familiar? On a large-enough map, all roads lead to Fusebox. The
>benefit of EPIAI is that what Fusebox can do in 10 files (5 QRY_'s and 5
>DSP_'s), EPIAI can do in one.
>
>
>
>
>
>=============================
>Matthew J. Vecera
>Accurate Imaging, Inc.
>668 American Legion Drive
>2nd Floor, North Side
>Teaneck, NJ 07666
>201-287-9300 tel
>201-287-1900 fax
>www.accurateimaging.com
>[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/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
