"Alex Shi" <[EMAIL PROTECTED]> wrote in message
> Basically I agree with you. But the second time to get time must be done
> after the page is rendered on local browser. So I suggest to use
> for the second time to get time, and pass the first time value into a js
> function.

As another person noted, there may be significant differences
between client and server clocks.  For accuracy, you must use
the same clock for both measurements - and you cannot use
the client-side clock, because javascript will not run until the
page is fully loaded.

How about this: embed 'start' and 'end' timestamps in the page
when it is generated, then use a javascript fake preload (call
another script instead of an image) to pass them back - the
time they are received is your timestamp for the page being
loaded.  This will obviously include a small additional delay for
the second request, but it should give you a close upper bound
on the actual time.

PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to