> I think i would p[ersonally tone down the fusebox methodology
> myself, it needs to be alot less complicated to trully be a catch
> all solution.
> When the fuse breaks its maddening, and is just another layer to
> run through to fix stuff.
There are a number of things about Fusebox that can be new ideas to absorb.
However I'm not quite sure I'd call *any* of it complicated. If anything, it
is too loosely simplified
as for the fuse breaking, that is a good use of <cfdefaultcase>, which will
catch all undefined fuses. If a known fuse breaks then you should have a
<cferror> tag throwing an error that tells you which fuse file it is in
anyway--if anything it is the CODE that is a problem at that point, not how
Fusebox has organized said code's execution. :)
i think someone once said "the fault lies not in the Fuse, but in ourselves"
:)
~~~~~~~~~~~~~ Paid Sponsorship ~~~~~~~~~~~~~
Get Your Own Dedicated Win2K Server! Instant Activation for $99/month w/Free Setup
from SoloServer PIII600 / 128 MB RAM / 20 GB HD / 24/7/365 Tech Support Visit
SoloServer, https://secure.irides.com/clientsetup.cfm.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
