Jim,
I was wondering why you removed the "last week" tab when you want to look back at post. You have "yesterday," and "past 24 hour" but you took away the "last week" one.

On the weekends, its hard for me to get to a computer, especially when I am away on my drill weekend like this past weekend. So, on Tuesdays when I come in to work, I like to catch up on what I missed.
It was just easier to click on the "last week" tab.

Just wondering.

Pete,

I believe it's Due to the Server change..... the casche is no longer that big......

Actually it was more the drain on the database. The "Latest Posts" page is somewhat of a resource hog as it is, and being able to call up the last 1200 active topics over the past week is a bit of overkill. I would suggest instead just using the forums as that is really how they are designed to be used. In other words each page only queries 10-50 topics so the overhead is kept lower.

Thanks,
Jim

Roger that Jim!

Hai Jim,

From this thread I suppose that the page is dynamically produced each time a user requests the information.

A suggestion. Is it not possible to make the "yesterday", "last week" and other resource consuming pages on a servertime basis instead of on request?

I would propose that the page is dynamically produced once, stored in a table and fetched each time a user requests it.

I have done something like that on another site (work related). I have now an object that sits between the user request and a few time consuming internal processes and queries.

The handler processing the user requests concults this object. If the object decides that the info in its dbase is still current enough then it immediately replies, otherwise it excecutes the original time conuming query, stores it in its dbase and gives the correct answer to the request handler.

This makes that some queries are only excecuted once an hour/day instead of with every user request.

It saves a lot of time and nobody notices

just my 0.002 cents

How about last 48 hours?

Paul