- This topic has 6 replies, 1 voice, and was last updated 17 years, 5 months ago by
.
-
Posts
-
-
Today it happened twice where I was trying to post a message and got
hit with the standard diclaimer when submitting. After agreeing,
it when back to the message listing and the post was lost. This
happened on both IE and Firefox, one on Windows, the other on Linux.The other problem seems to be with Firefox rendering. The tables
for the messages go quite a bit past the right margin of the white
field down the center. -
Chris:
Thanks for letting me know. As usual, the new BBS is ‘two steps forward, one step back’. You may have noticed that it got a little better today, and you can expect that it will get a little better tomorrow.
It’s a lot of new code, and we’re working the bugs out one by one.
Actually .. my focus for the next few days is on performance. We need to do a little bit more ‘tweaking’ and then we’ll focus on the browser compatibility issues.
Keep posting anything you notice here. Getting this right is at the top of the priority list!
-Ken W
-
-
So it was the session expiring? Makes sense…Sometimes I have a habit of starting a post, putting it to the background, and finishing it later. If I may make a suggestion, you might want to look at some sort of session keepalive algorithm. Throwing more time at the global timout variable masks the problem, but doesn’t get rid of it. For instance, I started this post about 5 hours ago and got busy doing something else. When I press Submit I’m probably going to get whacked by the session timeout. Must remember to copy and paste…Anyway, I searched the ‘Net for some code that could help you do this. Check out Session Defibrillator – it might fit the bill:
-
Chris:
Thanks … something is timing out the session variables faster than I’d like. I’m not sure what. I’ll check out the link you gave.
For now, if you are typing something long — type it first in Word (or, notepad) and copy/paste it into a message.
Why is nothing ever easy when a computer is involved?
-Ken W
-
Well you know how it is…1% of a program is telling the computer what to do, and 99% is patch jobs telling it what not to. I find the easiest system to maintain is one with no users on it. They are such whiners.
My feeling is that the sessions aren’t timing out sooner than you have defined; The session timeout should be whatever your global.asa file says it is. If you’ve set it for 40 minutes, that means I can sit here for 40 minutes while typing this message and not run into any submit problems. Any more than that, and it’s bye bye session. The link I sent you is a script that bounces traffic between the server and and idle web browser at an interval you define, which resets the session timer. This means you could set the global session timeout to be much, much less while laggards like me can spend eternity figuring out what to type.
-
-
