No, because once the page is rendered, many scopes simply go away (request
and variable being the two most important ones). By using these variables
to control what happens as we render a page we can choose from many paths,
but the bottom line is once that page is rendered, the memory needed to
engineer it is free'd up on the server. Heck, in one environment I worked
on, we had at any give time over 150 request variables...and some of them
were complex structures and multi-dimensional arrays. There is a toll to be
paid while the page is rendered in the form of speed and on the server in
the form of memory...but once its done...all is good. Besides...can you
think of another way to get what you want without using variables? Or
queries...remember that abusing a data server can be just as taxing on the
end-user in the form of wait time. Request away and be happy.
-----Original Message-----
From: Shawn Regan [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 10:29 AM
To: Fusebox
Subject: RE: my so many vars and dynamic stuff?
Just wanted to ask about all of the request.headergraphic,
request.myentirewebsite If you start loading everything into a variable
won't this start to take a toll on the cf server?
Shawn Regan
-----Original Message-----
From: Mike Craig [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 12:44 PM
To: Fusebox
Subject: RE: cfmodule or cfinclude with request variable
It's all good man. I have done something very similar very often and I
would recomment the request.headergraphic="" approach. This way, it can be
set at a circuit level, say in an app_locals.cfm or in an individual page of
"body content" so that when the header renders, the request variable already
exists and will be recognized by the header file. A module call (a.k.a.
function) would work fine too but I think it is unnecessary and might only
serve to clutter your index.cfm file.
Just my opinion, but I have worked in some very large environments and this
seemed to work best for me.
-----Original Message-----
From: Joshua D Rusch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 9:03 PM
To: Fusebox
Subject: cfmodule or cfinclude with request variable
Hello,
I am new to both fusebox and cold fusion, so bear with me please....
I've heard this list is pretty friendly, so I am not too worried:)
I have a file in my blocks directory that is a header. There is an image in
this header that varies from page to page. Is it better to have the image
name as a request variable that I set in my index.cfm switch statement, or
should I do something like <cfmodule headerimage="testimage.jpg"> and then
in my header file use attributes.headerimage as the image?
Are there advantages/disadvantages to both? Are they both valid fusebox?
(Well, I'm pretty certain the 2nd method is valid)
Thanks,
Josh
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
