(Sorry if this is a bit dated, but I've had better things to do than read
email lately)
Hal, if I'm getting this correctly, you need a variable scope that's more or
less local, but can still be accessed from custom tags, modules whereever.
Why not switch to one of the other two (security implications aside, NAT (I
won't mention names) scopes? (ahem... speaking of either url or form)
both are less typing and are available even to templates called as
customtags/modules. You now have the usual five
(server,application,session,client,cookie) other global scopes, (like
request) for your "secured" variables. and use either form. or url for you
public scoped variable (both of which can be looped through without much
ado, unlike that yukky Variables scope) Seems to me like it would solve
most of your problems without compromising your site's security.
I would think this should handle everything you need, and won't be so hard
for the other old timers to swallow and/or adapt to. Now, whether you'll
get everyone to take to XFB which to me is a marriage of BlackBox and
Fusebox, with a hit of SmartObjects (Not knocking it, FB was originally
sold me on the fact that it was really just a collection of practices that
worked well for everybody, and had good foundation), I just don't like the
overhead involved, and feel its too "Spectra" like for my tastes. Like I've
always said though, do what works best for you.
Fred
----- Original Message -----
From: "Hal Helms" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Sunday, March 25, 2001 11:36 PM
Subject: RE: Musings on Attributes (was Best Practices...)
> Well, the whole idea of XFB is that you DO know EXACTLY what vars you're
> getting in before you write the first line of code (via Fusedocs). I treat
> ALL scopes as a single entity in thinking about naming, so I would not
have
> a local variable with the same name as a request variable, an attributes
> variable, etc. I find this is just integral to the way I write code and I
> would be very uneasy with relying on scopes to differentiate variable
names.
>
> Hal Helms
> Team Allaire
> [ See www.halhelms.com <http://www.halhelms.com> for info on training
> classes ]
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
