but I tend to view sessions as something that consumes memory - they
may be something
that holds database tables open, and may even be causing CPU to be
consumed, even
though a user may not be actively hitting the server with new requests.

A session is nothing more than a hunk of memory (assuming in-memory
sessions) sitting on the server. Shouldn't consume CPU, and I don't see
it holding any locks in the DB. I guess in theory I could start a
transaction and then store the transaction in session, never tried,
never would.

-Walden


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.