From: Walden H. Leverich
Maintaining session is something all web-application developers
have to deal with.

I appreciated your observations about in-process, out-of-process, and even offloading session management to remote state management & database servers. And that it's an issue that is addressed by developers and architects, although perhaps supported by frameworks.

The subject of expiring sessions after a period of inactivity has been mentioned several times, but has anyone considered limiting the number of sessions - just redirecting the browser to a static page telling them that a configured session limit has been reached - try back later? Say you have an idea of how many sessions your server can support before overload occurs. Wouldn't it be better to tell some users to come back later, rather than fight over resources? Are there frameworks that support that?

Nathan.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.