> The overhead comes into play when an an exception is thrown > and the cfcatch portio executes... especially if you have multiple > cfcatch tags that are not in the best order, e.g. the most specific > being first then so on down to the most general.
At that point, though, overhead is probably not your primary concern (or even an important concern at all). After all, exceptions are, well, exceptional, by their very nature, so you shouldn't have to deal with too many of them at once. As for the ordering of your CFCATCH tags, again that's not really a performance issue but rather a logic issue - you don't want to catch an exception as a general type if it could be caught as a specific type. I really doubt there's any significant time spent by CF going through the list of possible exceptions you're trying to catch and matching the exception you have against that list. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211991 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
