Hey boys & girls,
I'm doing some maintenance work on a site that
allows members to keep a personal library of podcasts.
One thing the site does it every time the personal
list of casts is viewed, it goes out and gets the
most current episode information for each cast in
the user's list, but this slows the display of the
page down quite a bit, not too bad for 6 or 8
casts, but if the user's start adding many more
than that it gets noticably slower.
My idea is a cron job that runs in the background
that checks to see when the last time a cast was
updated with episode data, and if a preconfigured
amount of time has lapsed, it reads the XML file
and udpates the DB.
Having never dealt with podcasts before, I'm
feeling a bit like I'm flying blind, so the issues
I'm wondering about are:
1) Some podcasts are updated weekly, others daily,
etc, so updating a weekly podcast every few hours
would be overkill.
2) Reading the XML file from the source feed is
time consuming. If the site ends up with thousands
of casts, this could pretty much kill the cron job.
I'm wondering if anyone on the list has dealt with
this kind of thing and what kind of strategies
were employed.
Any suggestions would be greatly appreciated.
--
Skip Evans
Big Sky Penguin, LLC
61 W Broadway
Butte, Montana 59701
406-782-2240
=-=-=-=-=-=-=-=-=-=-=
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
