> The only question left in my mind is whether it's worth
> bringing in genuine attribute-scoped variables as well.
> The only case where you would need this is if you were going to
> call the app as a custom tag, and I think we're finding that
> case to be quite uncommon.
Jeff,
In common cases, the attributes scope would be empty, right? So there
shouldn't be any significant performance hit in copying it over along along
with the URL scope.
For me, making a copy of attributes would be necessary... at least one of my
forthcoming apps will be "syndicating" its content to the non-FB parts of
the site via a custom tag interface. And since I don't forsee a need to pass
any 80,000 character strings into the custom tags in question, any impact on
performance should still be slight.
Which leaves us with an uncommon action within an uncommon case... someone
calling an FB app as a custom tag *and* passing in big, memory hogging
attributes. It could certainly happen, but I don't see it as a major
concern.
--
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
