It of course depends on how frequently the data is needed as well. If the data is being requested a lot more frequently than the data is updated, doing a static page that is updated outside the http request is the faster way to do things. If the page is requested less frequently or barely more frequently than the page's data is updated, doing a static page doesn't help much. This is also true if the page is different for different users (prime examples of course are Slashdot's homepage vs. its story pages).(some people will consider this different then I do)
The information isn't something that needs "live content" as it really doesn't change that often. If the cache is updated daily with specific areas being updated every couple of hours, it would be fine. That is why that might be an option. However, it might be easier to switch from MSSQL to MySQL if MySQL would handle the traffic better. We do need a little logic to determine if the user is logged in (if they aren't logged in, they don't see the page) but it shouldn't be all that complicated.
thanks.
benji
---
Ben Spencer
Web Support
[EMAIL PROTECTED]
x 2288
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
