|
Hi all, especially Robert.
On another thread I mentioned that my long posts were "timing out" and you indicated that should only happen after a full hour. I didn't believe I had spent quite that much time on any of those posts, but I've had the problem on another thread that I'm certain I didn't spend more than 20 minutes writing. Fortunately, I copied my text before submitting, so nothing was lost.
I don't know if it happens when the website is running slowly (as it seems to be right now) or in association with other errors (I had trouble navigating back to the messageboard because of a server issue... Shortly after finding out that the "page is not available". So, make of it what you will.
PS - I'd still like e-mail notification of posts - I know that has been on the "to do" list, but it would be swell.
Hi all, especially Robert.
Hi!
On another thread I mentioned that my long posts were "timing out" and you indicated that should only happen after a full hour. I didn't believe I had spent quite that much time on any of those posts, but I've had the problem on another thread that I'm certain I didn't spend more than 20 minutes writing. Fortunately, I copied my text before submitting, so nothing was lost.
Hmm. There are some other possible technical explanations for why this might happen occasionally, such as if we roll new code or if the site or server cycles while you are composing a post. If it's happening consistently, as you seem to indicate, then it's possibly a general session management issue. Anyway, we'll keep looking into it.
PS - I'd still like e-mail notification of posts - I know that has been on the "to do" list, but it would be swell.
Noted. : )
Senior Software Developer
|
Typically once you begin writing a post, your session should only time out after an hour.
However, there are a couple other reasons why the server may forget who you are and what you're doing (which is essentially what happens when the session times out -- it doesn't know what to do with the post you're submitting).
These circumstances include when the application instance you're on crashes, or when we shut it down either manually or automatically. We're hard at work every day fixing the bugs that cause crashes. Manual and automatic shutdowns are usually "graceful", in that we try not to dump any active sessions. Sometimes, however, we have to shut off an instance immediately because we're rolling out new code that's incompatible with the code that's already running.
(On preview, what Rob said. :-)