Lloyd Hannesson has a solution for caching your blogrols (if you are using blogrolling.com). It's a little tricky and requires a PHP extension (Cache Lite) be installed on your server. If you can arrange that then you should be in business.
He's also working on an idea we've been talking about back and forth via e-mail for a chron job to do the caching (which would not require any extra modules be installed by your host). The chron job would guarantee that you always serve a local copy of your blogroll. If Blogrolling.com is down for an extended period your blogroll would still be served - just not updated from Blogrolling.com. Once Blogrolling.com comes back on line the chron job will update your local copy.
That gives you the power of managing your blogrolls with the existing Blogrolling.com interface, and freedom from dependence on their servers to quickly load your page. As soon as that script is running here my blogrolls will return to the front page.



Comments (2)
I'm not completely up on th... (Below threshold)1. Posted by Paul | May 24, 2004 12:42 AM | Score: 0 (0 votes cast)
I'm not completely up on the whole blogrolling thing but the chron job seems like a far more efficient and elegant system.
Is there a hold up.. It seems like that should be trivial no?
1. Posted by Paul | May 24, 2004 12:42 AM |
Score: 0 (0 votes cast)
Posted on May 24, 2004 00:42
2. Posted by Kevin | May 24, 2004 10:14 PM | Score: 0 (0 votes cast)
Not trivial, but not overly complex. Since you are dealing with data boming from another site in raw form you have to build in a few levels of error checking to make sure you get data not a jumble.
It's running here now...
2. Posted by Kevin | May 24, 2004 10:14 PM |
Score: 0 (0 votes cast)
Posted on May 24, 2004 22:14