Re: Using database driven pages
To get around the mirroring issue, you could store the data into a
database but use a cron script to generate the vendor pages at a
pre-selected time. This is done in high traffic sites with data that
doesn't change that often or when you don't need to see the changes
until the next export. For the vendors page, a 24 hour lag is
probably ok.
Thalia
> As a rule... just plan on NO mirroring of CGI driven pages...
>
> On Wed, Apr 26, 2000 at 09:59:37AM +1000, Craig Small wrote:
> > G'day,
> > The Debian Vendors page is getting rather large and, well a bit hard
> > to manage and read. I am thinking a database driven page would make
> > things easier for everyone.
> >
> > I'd like to discuss with everyone here wether or not we agree that this
> > is a good idea and if so how to implement it. I don't think the entire
> > Debian website should be database driven, but certainly some parts could
> > benefit from it.
> >
> > As far as loading is concerned, I just did a quick grep of the
> > access.log and found 833 accesses to the vendors page between
> > 6am to 5pm, so we can assume, say, 1600 accesses a day for that page at
> > least.
> >
> > I'm not sure how many hits the mirrors get.
> >
> > - Craig
> > --
> > Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA
> Please cc all mailing list replies to me, also.
>* http://benham.net/index.html <gecko@benham.net>
Reply to: