Like several other people have mentioned I've built a bunch of tags and
routines that make heavy use of the fact that I can grab everything I need
from the attributes scope. Dumping it into the variables scope would screw
up all kinds of things. I LIKE my scopes to be seperate...
Toby Tremayne
Code Poet and Zen Master of the Heavy Sleep
Show Ads Interactive
359 Plummer St
Port Melbourne
VIC 3207
P +61 3 9245 1247
F +61 3 9646 9814
ICQ UIN 13107913
-----Original Message-----
From: BORKMAN Lee [mailto:[EMAIL PROTECTED]]
Sent: Saturday, 24 March 2001 10:03 AM
To: Fusebox
Subject: RE: Musings on Attributes (was Best Practices...)
Yes, my main concern about XFB is that the fuseboxes do in fact have to
be nested. That means if I want to re-use my login circuit in multiple
applications, I have to make multiple COPIES of it nested in each app.
If I can just use CFMODULE to call the login app, then I can just have
one copy and one alone. Mind you, I think that XFB can actually be
adapted to make use of pseudo-nested circuits - ie, circuits that
function as though they are nested ("inheriting" environment variables
from the home app), while actually living outside the home app's tree.
The real reason for FOMRURL2ATTRIBUTES is so we can get the maximum
re-use for our code. It means I can use a single InsertData fuseaction,
but call it in many different ways, from a form, as a CustomTag, with
data in a URL, etc. I haven't done any benchmarking, but let's be
honest - how much data are we usually passing around? File fields might
well be a special case that we should think about - I sure wouldn't ever
want to pass that data as a URL. But normally, gee, I have ten or
twenty fields, a few bytes each. Can this really be of any significance
compared to normal webby network/connection speeds?
See you all soon,
Hope this isn't going to turn into a proper fight between our own Lenin
and Trotsky!!
LBB.
-----Original Message-----
From: Roger B.
Steve,
Same here... the whole XFB nesting thing strikes me as a beautiful mess
that
solves a non-problem. Custom tags are a fundamental part of CF, and to
me,
they have always seemed the cleanest, most natural way of calling
another
'box.
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
