> The problem (and I assume quite a known one) I had previously was that
> application scope variables could be read by cfincludes, but not by custom
> tags since they are in their own memory space.
Matt,
That's not accurate... custom tags can, in fact, see application variables.
> This appears to be ... the purpose of using
> the request
> scope -- that it works for both cfincludes and custom tags. Is
> this correct?
No, the request scope is used to avoid the locking issues that come with
application variables. The theory is that any overhead generated by
repeatedly setting request variables is offset by the decrease in code
complexity and overhead that results from the elimination of multiple
CFLOCKs.
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
