It would depend on your requirements, for example setting the application
variable means that it now becomes a global variable. However when you come
to use the date, depending on when you set the variable it will hold the
incorrect time stamp. Unless this is not a problem for you.
My solution would be if this function isn't that fussed if the time stamp is
out by a few seconds or however long it takes to run. You could set the
variable once at the beginnning of the function and reference this variable
where you need to instead of calling the now function everytime.
regards
Andrew Scott
Senior Cold Fusion Application Developer
ANZ eCommerce Centre
* Ph 9273 0693
* [EMAIL PROTECTED]
-----Original Message-----
From: Jon Hall [mailto:[EMAIL PROTECTED]]
Sent: 24 November 2000 18:42
To: CF-Talk
Subject: which is faster?
This is a multi-part message in MIME format.
------=_NextPart_000_0017_01C055C0.165A91D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I have a calendar app that calls the now() function many times =
throughtout and format it differently using the day(), month() and so on =
functions. I got a thought that it may be faster just to set the now() =
value to a variable in the application.cfm so I dont have to =
contininually call that function.=20
Would this show any speed increase?
jon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
