I will try to explain my reasoning.
Even though the recent logs job runs every 15
minutes, the time it takes for the job to complete
might be anywhere from a few seconds to 5 minutes
(depending on the Perl script's throttle setting and
how many new log details have to be looked up).
To add to the complexity of timing, there is no
good way to sychronize the 15 minute update
schedule of geostl.com with the 15 minute update
schedule of geocaching.com. It is best to assume
they are never in-synch.
The third part of the equation is where within
these two disparate processes a user decides
to open up the Recent Logs page.
So, to give the user a better chance to see more
new data more quickly, I made the browser refresh
rate shorter than 15 minutes so the overlap of the
schedules will be in their favor.
--------------------------
Glenn wrote:
> >
> >If the job to update the recent log page runs every 15 minutes, why does
> >the page automatically refresh itself after 10 minutes (600 seconds)?
> >Why not do the automatic refresh after 15 minutes to coordinate with the
> >job?
> >
> >Just wondering....
> >
****************************************************************************
> > Our WebPage! Http://WWW.GeoStL.com
> > Mail List Info.
> > //www.freelists.org/cgi-bin/list?list_id=geocaching
> >***********************************************************************
*****
>
> ----------------
> Glenn
