|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
 |
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
|
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
Dev Articles Community Forums Sponsor:
|
|
|
|
#1
November 28th, 2002, 11:26 PM
|
|||
|
|||
|
Article Discussion: When Session Variables Go Bad
When Session Variables Go Bad If you have any questions or comments about this article then please post them here.
You can read the article here .
|
|
#2
February 17th, 2004, 11:16 PM
|
|||
|
|||
|
when you set session variables to undefined.
I was wondering. Since session variables have a high memory cost. Does this mean if you set the session variable to "undefined" after its use would this reclaim any memory associated with the use of the session variable? If not just when does the memory get reclaimed from the session variables used?
|
|
| Viewing: Dev Articles Community Forums > Programming > Programming Tools > Article Discussion: When Session Variables Go Bad |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
