Michael E. Locasto typed the following on 08:00 PM 6/18/2002 -0400 >I've done a bit of thinking and came up with a mechanism that might >solve both issues of wasted memory and "lost" users. It involves >persistent storage of "retired" sessions, so if this is actually how >LRUMap or the session Manager works, I apologize.
PersistantManager can be configured to do exactly this - you set a time limit, shorter than the expiration limit, after which a session is swapped out to disk (or DB). You can also configure the maximum number of sessions to keep in memory, and swap out older sessions when that limit is exceeded. For the default behavior, I'm much more comfortable blocking new users over the limit than quietly dropping old users. Explaining to users why their session has been dropped would be ugly, both to implement and as a user experience. Simply dropping their session early is going to be confusing, it will make the webapp (and Tomcat) appear unpredictable and unreliable from the user's point of view. Showing a page to new users saying the server can't handle any new connections is kind of ugly also, but it's standard behavior. To add another imperfect analogy, FTP servers don't cut off connected users when their limit has been reached: new users are told they have to wait. I'm +1 on keeping the current behavior when the max is reached, +0 on adding a default limit. Kief -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
