I thought I would bring this up here since Farcry makes a lot of use of cfincludes within cffunctions.
Some people have discovered a bug/problem with using cfcs and cfinclude in that using cfinclude effectively eliminates any chance of making a cffunction thread-safe. http://www.camdenfamily.com/morpheus/blog/index.cfm?mode=entry&entry=60EE263F-C9FD-43B5-ED1FD4C7B0343055 For instance, in tree.cfc (which is application-scoped so it is vulnerable to thread-safety issues), many of the function's bodies are cfincluded. Technically, it is feasable that one cffunction inovacation would receive another's result. Now, I know most of the work that farcry does is not exposed under heavy load due to caching, however I'm wondering if a lot of the persistant CFCs should be updated to "best-practice" in terms of thread safety, which means: -no cfinclude -var EVERYTHING, even names of cfqueries and iterators thoughts? -dave --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
