| Author |
 Topic  |
|
Nathan
Help Moderator
USA
7664 Posts |
 Posted - 13 August 2002 : 18:54:36
|
| The difference will probably be infantisimal, but the start timer code should probably be at the top of config.asp, not inc_header.asp |
 Nathan Bales
CoreBoard | Active Users Download |
|
|
alex042
Average Member
USA
631 Posts |
Posted - 14 August 2002 : 09:36:14
|
quote:
The difference will probably be infantisimal, but the start timer code should probably be at the top of config.asp, not inc_header.asp
I guess that depends on when you want to start timing page loads. I would assume you'd want this a the start of a page load so whichever the page would call first.
|
 |
|
|
snaayk
Senior Member
USA
1061 Posts |
Posted - 14 August 2002 : 10:42:02
|
quote:
Originally posted by alex042
quote:
The difference will probably be infantisimal, but the start timer code should probably be at the top of config.asp, not inc_header.asp
I guess that depends on when you want to start timing page loads. I would assume you'd want this a the start of a page load so whichever the page would call first.
That was the point,  |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 14 August 2002 : 11:38:54
|
| inc_func_common.asp is included at the very top of inc_header.asp. Doesn't that mean that that is where the start timer code should be then? |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 14 August 2002 : 14:42:32
|
config.asp is the first code to run. If you start the timer in inc_header.asp then you are excluding any processing time for config.asp.
Nathan is right on all points, the difference probably isn't significant unless the app variables need to be loaded (one time only).
|
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 14 August 2002 : 15:16:02
|
| Since whether or not the Timer shows depends on the strShowTimer variable, which is stored in an Application Variable, we would have to put the timer code below where the Application Variables are defined. |
|
|
|
Nathan
Help Moderator
USA
7664 Posts |
Posted - 14 August 2002 : 15:41:41
|
| Why would starting the timer depend on whether or not its going to be output? (outputted?) |
Nathan Bales
CoreBoard | Active Users Download |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 14 August 2002 : 15:49:43
|
| I will guess strShowTimer variable is used only in inc_footer.asp (or whatever the new name for the file), to determine whether to display Load Time or not. If so, Timer Code can be put at the top of config.asp, whether or not strTimerCode variable is initialized or not. |
Edited by - GauravBhabu on 14 August 2002 15:51:20 |
|
|
|
alex042
Average Member
USA
631 Posts |
Posted - 14 August 2002 : 15:54:39
|
quote:
Since whether or not the Timer shows depends on the strShowTimer variable, which is stored in an Application Variable, we would have to put the timer code below where the Application Variables are defined.
This must be a new variable. This makes some sense if starting the timer code requires an application variable. That application variable would have to be defined before it could be used.
quote:
I will guess strShowTimer variable is used only in inc_footer.asp (or whatever the new name for the file), to determine whether to display Load Time or not. If so, Timer Code can be put at the top of config.asp, whether or not strTimerCode variable is initialized or not.
From the previous response, my guess is that there's a check prior to even running the timer script to determine whether to even bother running the timer code or not. If it's not going to show anyway, there's little point in running the script.
|
Edited by - alex042 on 14 August 2002 15:57:32 |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 14 August 2002 : 16:04:30
|
| The point in discussion here is to determine the Total Time to process the Page. So Start and Stop the Timer without any check and use the variable only to determine whether or not to Display the Page Process/Laod Time. |
|
|
|
Nathan
Help Moderator
USA
7664 Posts |
Posted - 14 August 2002 : 19:25:16
|
Exactly. For an analogy, if your going to work, you dont go to your boss before chcking in, only to get your paycheck  |
Nathan Bales
CoreBoard | Active Users Download |
|
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 14 August 2002 : 20:38:39
|
| Does anyone forsee any ill effects if the Timer isn't stopped? Such as with windows that use inc_footer_short.asp ? |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 14 August 2002 : 20:44:30
|
Isn't inc_footer_short.asp used with inc_header_short.asp.  |
|
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 14 August 2002 : 20:46:25
|
| I thought y'all wanted to move the timer code to the top of config.asp |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 14 August 2002 : 20:56:22
|
When timer is started in config.asp, both StartTimer and StopTimer functions will also be moved to config.asp Will there be a scenario, when the function StopTimer won't be accessible from inc_footer_short.asp, incase function StopTimer is called from inc_footer_short.asp.
If that is what is your concern
|
|
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 14 August 2002 : 21:03:45
|
| we don't currently stop the timer in inc_footer_short.asp because it isn't used in popup windows. Why assign a resource if it's not even going to be used? Why start and stop a timer if the value isn't going to be used? |
|
|
|
Topic |
|
Topic Locked
