The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:This is not reliable. If the browser crashes, then the JavaScript will not execute. Nor will it execute if the user has JavaScript disabled. It can also lead to problems for people like me who open multiple tabs on the same application - for example, when I'm shopping a web store and want to compare various possible purchases without continually re-fetching pages.
The safest way to manage something like this is to shorten the web.xml timeout value to whatever is reasonable for the application.
If you do intend to send a formal logout notification, I suggest that you preceed it with a confirmation dialog.
And if you really have IE5/IE6 clients, I sympathize.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:I don't know if I understand perfectly, but I'll try.
I don't know what "created a field in DB status" is, but you can add a sessionListener to your webapp that can cancel any work in progress in the event of a session being terminated. Unlike client-side timeouts, this should always work. In fact, it should theoretically even work if you send a shutdown request to the webapp while users are logged in.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:
Based on what you are describing, however, I can virtually guarantee that you are not using the J2EE login security system, which means that security is almost certainly not very good anyway.
Don't get me started about those stupid light bulbs. |