> Roger argues that it's important to differentiate between
> incoming and local parameters. "Attributes" actually blurs
> the differentiation, because it's used both as an incoming and
> a local scope.
Patrick,
Not in my methodology. Any given member of the attributes structure is
touched (at most) one time... when it is copied in via FU2A in app_globals,
or when it is CFPARAM'd into existence within a single CFCASE.
Hm... your comment has me wondering about something, though. How common is
the practice of changing the value of attributes during the processing of a
fuseaction? Are people out there routinely adding things like XFAs to
attributes, or treating the scope as a central repository for "Fusebox
variables" of all kinds, including those that are modified on-the-fly?
If so, I can kind of understand where some of the confusion and opposition
is coming from... although for the life of me, I can't understand why anyone
started doing that in the first place.
> If it's important to you to know if a variable came from outside
> the fuse (a VERY, VERY bad idea, IMHO, because a circuit isn't
> supposed to know about its environment), you still have the
> original, untouched FORM, URL, and ATTRIBUTES scopes.
Using three distinct, incoming scopes cripples the custom tag powers of
Fusebox. That's unacceptable for my uses.
And no matter what you do, there is *some* point where your circuit has to
ask questions about the environment... even if it's just at the point where
you copy the form, URL, and attributes scopes into Variables.
--
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
