I couldn't immediately locate Joe's comment so I'm not sure exactly what he meant but here's my guess. Mudcat forum pages are not displayed from stored text but are generated dynamically each time a link to a page is invoked. When we (left) click on a thread link, the thread page is loaded and generates the latest index for the thread in question along with all the posts. When we click our browser's back button, we aren't simply moving back to a cached page, we are actually causing the Mudcat server to generate a new, possibly revised, list of threads. I'm guessing that it's the constant regeneration of the threads list that Joe says is placing a load on Mudcat's computing resources.

If we shift-click the thread links or right-click and select Open in New Window, we preserve our current thread list. Then, when we close the new thread window, we are returned to our thread list without asking a Mudcat server to generate a new one.

If my explanation is off base, I'm sure Joe (or a clone) will be along to set me straight.

      - Mark