CreeDo:
When you say a timeout, do you mean there's a significant period of time before the page finally displays? Or the page NEVER displays and instead gives you an error that the server didn't respond / page not found?
I'm not sure the cookie incident is related to this, as like you said, this was in the past and preceded my involvement (i.e. methinks Mike ironed that one out -- might've been db/content-related, I don't know). Thanks for sharing that, though -- if you encounter that again, let us know.
I do know this, though -- if you start a post reply, get side-tracked (for a significant period of time), and then come back to your reply to finish it, only to encounter an expired cookie or a timeout -- is NORMAL on a cookie-based website. That's a function on the expiry time on the cookie itself, and in the case of replying to posts on forums (which is a dynamic entity), those cookies (and the TCP session associated with it) are usually short-lived. This happens on shopping carts on websites as well -- it's normal for these (the cookies and the TCP session) to expire in a short amount of time, both for security reasons, as well not holding resources up on the server (i.e. the TCP session itself). What I typically do, just before I walk away on my "sidetrack" -- is to copy the text I typed to the clipboard (press [Ctrl] [A] to select all, and then [Ctrl] [C] to copy it to the clipboard). Then, when I come back to it, I know I'm going to have an expired session, so I just press the [Back] button on the browser, refresh the thread, re-respond to that post I was previously responding to, and press [Ctrl] [V] to paste what's on the clipboard back into the reply text field. I can then finish it from there.
I'll try and see if I can duplicate what you encountered, by replying in a couple threads. I'll also PM a couple folks, just to see if I can exercise it from that point as well.
Thanks for sharing this!
-Sean
Sean, if there are touch points within the software where delay occurs and it's not truly random, would that not imply that it's a database/vBulletin issue?