> index.cfm in a cftry essentially wraps the entire request in
> a cftry does it not?... Potentially hindering performance?
In general, using CFTRY/CFCATCH doesn't add any significant overhead unless
an exception is thrown, in which case you generally don't mind the overhead.
The problem with wrapping an entire page with CFTRY is that it doesn't allow
you to deal with specific problems very well. Ideally, you want to wrap each
problematic section of code with its own CFTRY, so that you can capture the
specific exceptions that are likely to occur with that piece of code only.
If you find yourself using CFTRY around very large blocks of code, you might
be better off just using CFERROR.
I would also like to voice agreement with Barney's disapproval of premature
optimization concerns.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
