
December 18th, 2006, 09:45 PM
| | | preventing session variables from going null
In ASP classic pages, I want to know if it's possible to prevent
session variables from becoming zero length strings? I have tried
setting the Session.Timeout to a large value, but alwas, after 20
minutes, my session variable times out. I also tried setting the
session timeout in IIS manager to a high value, but this did no good
either.
I just want to allow one particular session variable to last a long
time. Any other suggestions? \
Thanks. | 
December 18th, 2006, 10:15 PM
| | | Re: preventing session variables from going null
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166477890.936053.37180@80g2000cwy.googlegrou ps.com... Quote:
In ASP classic pages, I want to know if it's possible to prevent
session variables from becoming zero length strings? I have tried
setting the Session.Timeout to a large value, but alwas, after 20
minutes, my session variable times out. I also tried setting the
session timeout in IIS manager to a high value, but this did no good
either.
>
I just want to allow one particular session variable to last a long
time. Any other suggestions? \
>
| Session Variables live as long as the session (unless you explicitly
terminate them before that). If you want a value to persist beyond the life
of a session, then by definition, this can't be done using a session
variable. You will need to use a different mechanism - database/text
file/application variable...
--
Mike Brind | 
December 18th, 2006, 11:25 PM
| | | Re: preventing session variables from going null
Mike Brind wrote on 18 dec 2006 in
microsoft.public.inetserver.asp.general: Quote:
>
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166477890.936053.37180@80g2000cwy.googlegrou ps.com... Quote:
>In ASP classic pages, I want to know if it's possible to prevent
>session variables from becoming zero length strings? I have tried
>setting the Session.Timeout to a large value, but alwas, after 20
>minutes, my session variable times out. I also tried setting the
>session timeout in IIS manager to a high value, but this did no good
>either.
>>
>I just want to allow one particular session variable to last a long
>time. Any other suggestions? \
>>
| >
Session Variables live as long as the session (unless you explicitly
terminate them before that). If you want a value to persist beyond
the life of a session, then by definition, this can't be done using a
session variable. You will need to use a different mechanism -
database/text file/application variable...
| In other words:
Session variables never time out,
they just fade away ...
.... when the session ends.
Preventing the session from ending is all that is required.
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress) | 
December 19th, 2006, 09:15 AM
| | | Re: preventing session variables from going null
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166477890.936053.37180@80g2000cwy.googlegrou ps.com... Quote:
In ASP classic pages, I want to know if it's possible to prevent
session variables from becoming zero length strings? I have tried
setting the Session.Timeout to a large value, but alwas, after 20
minutes, my session variable times out. I also tried setting the
session timeout in IIS manager to a high value, but this did no good
either.
>
I just want to allow one particular session variable to last a long
time. Any other suggestions? \
| That's strange. Session variables should survive for at least the period
specified as the session timeout in IIS Manager.
Is this Win2K3 IIS6? If so do you have periodic recycling enabled on the
application pool your ASP app belongs to?
You are aware that if you close your browser you are no longer able to
access the session, right? | 
December 19th, 2006, 01:45 PM
| | | Re: preventing session variables from going null
I'm aware of how session variables work, but can't figure out why the
session timeout settings are being ignored. I can't find anything in
the code (300+ pages worth) that would explain why this particular
variable gets set to "", but there is got that checks if the value is
set to "", and if so, it closes the browser.
I know the server is Windows Server 2003, SP1, if that helps.
Thanks.
Anthony Jones wrote: Quote:
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166477890.936053.37180@80g2000cwy.googlegrou ps.com... Quote:
In ASP classic pages, I want to know if it's possible to prevent
session variables from becoming zero length strings? I have tried
setting the Session.Timeout to a large value, but alwas, after 20
minutes, my session variable times out. I also tried setting the
session timeout in IIS manager to a high value, but this did no good
either.
I just want to allow one particular session variable to last a long
time. Any other suggestions? \
| >
That's strange. Session variables should survive for at least the period
specified as the session timeout in IIS Manager.
>
Is this Win2K3 IIS6? If so do you have periodic recycling enabled on the
application pool your ASP app belongs to?
>
You are aware that if you close your browser you are no longer able to
access the session, right?
>
> | | 
December 19th, 2006, 03:55 PM
| | | Re: preventing session variables from going null
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166535849.215623.150540@79g2000cws.googlegro ups.com... Quote:
I'm aware of how session variables work, but can't figure out why the
session timeout settings are being ignored. I can't find anything in
the code (300+ pages worth) that would explain why this particular
variable gets set to ""
| Is it really getting set to "" or is in fact Empty (test using IsEmpty
function)?
'why this particular variable gets set to ""' suggest that you have other
session variables that survive longer, is that so? | 
January 4th, 2007, 07:45 PM
| | | Re: preventing session variables from going null
Just getting back from vacation here. Well, I don't know why it gets
set to "", to be quite honest. From what I see, there is no code that
actually sets it to "", so I assumed it was happening when the
session.timout expired. I can't think of anything else, but I guess I
can try the IsEmpty function and see what happens.
Thanks.
Anthony Jones wrote: Quote:
"javelin" <google.1.jvmail@spamgourmet.comwrote in message
news:1166535849.215623.150540@79g2000cws.googlegro ups.com... Quote:
I'm aware of how session variables work, but can't figure out why the
session timeout settings are being ignored. I can't find anything in
the code (300+ pages worth) that would explain why this particular
variable gets set to ""
| >
Is it really getting set to "" or is in fact Empty (test using IsEmpty
function)?
'why this particular variable gets set to ""' suggest that you have other
session variables that survive longer, is that so?
| |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is Off | | | | | | What is Bytes?
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over network members.
|