Hello,
can anybody tell me how I can extend the session
expiry time? Is it done via code or via IIS? Sorry I am
new and dont know about this.
11  2973 
In code, it is Session.Timeout http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl... Hello,
can anybody tell me how I can extend the session
expiry time? Is it done via code or via IIS? Sorry I am
new and dont know about this.
where do you suggest to set this at?
I've heard in the web.config file:
<sessionState mode="InProc" timeout="60">
but I can't seem to get that to work?
What about the global.asax file?
I thought that page by page is over kill?
thanx.
"Ken Cox [Microsoft MVP]" wrote: In code, it is Session.Timeout
http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl... Hello,
can anybody tell me how I can extend the session
expiry time? Is it done via code or via IIS? Sorry I am
new and dont know about this.
The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com... where do you suggest to set this at?
I've heard in the web.config file:
<sessionState mode="InProc" timeout="60">
but I can't seem to get that to work?
What about the global.asax file?
I thought that page by page is over kill?
thanx.
"Ken Cox [Microsoft MVP]" wrote:
In code, it is Session.Timeout
http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl... > Hello,
>
> can anybody tell me how I can extend the session
> expiry time? Is it done via code or via IIS? Sorry I am
> new and dont know about this.
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system ( http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
And it only executes when using InProc mode.
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ep**************@TK2MSFTNGP15.phx.gbl... The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com... where do you suggest to set this at?
I've heard in the web.config file:
<sessionState mode="InProc" timeout="60">
but I can't seem to get that to work?
What about the global.asax file?
I thought that page by page is over kill?
thanx.
"Ken Cox [Microsoft MVP]" wrote:
In code, it is Session.Timeout
http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl...
> Hello,
>
> can anybody tell me how I can extend the session
> expiry time? Is it done via code or via IIS? Sorry I am
> new and dont know about this.
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
re: And it only executes when using InProc mode.
Absolutely.
Sometimes, since 99% of developers use Inproc,
we tend to ignore the more complicated scenarios.
Thanks for pointing that out.
We also need to remember that for Session_OnEnd to fire,
the session state has to exist first, meaning that you have to
have stored some data in the session state and must have
completed at least one request for the session data.
If at least one session data item has not been stored and
requested at least once, Session_OnEnd won't fire, either.
Juan T. Llibre
ASP.NET MVP
===========
"MattC" <m@m.com> wrote in message
news:u4**************@TK2MSFTNGP14.phx.gbl... And it only executes when using InProc mode.
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ep**************@TK2MSFTNGP15.phx.gbl... The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com... where do you suggest to set this at?
I've heard in the web.config file:
<sessionState mode="InProc" timeout="60">
but I can't seem to get that to work?
What about the global.asax file?
I thought that page by page is over kill?
thanx.
"Ken Cox [Microsoft MVP]" wrote:
In code, it is Session.Timeout
http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl...
> Hello,
>
> can anybody tell me how I can extend the session
> expiry time? Is it done via code or via IIS? Sorry I am
> new and dont know about this.
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
The question still is, say if you do want to chnage it from the default value
of 20 minutes, where is it best change it at?
"Juan T. Llibre" wrote: The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com... where do you suggest to set this at?
I've heard in the web.config file:
<sessionState mode="InProc" timeout="60">
but I can't seem to get that to work?
What about the global.asax file?
I thought that page by page is over kill?
thanx.
"Ken Cox [Microsoft MVP]" wrote:
In code, it is Session.Timeout
http://msdn.microsoft.com/library/de..._sesoptime.asp
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:14****************************@phx.gbl...
> Hello,
>
> can anybody tell me how I can extend the session
> expiry time? Is it done via code or via IIS? Sorry I am
> new and dont know about this.
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
That would depend on whether you want the
new value to be a globally applied value,
or whether you only want the session time
extended for users who access specific pages.
If you want the value applied globally, set it in web.config.
If you want the session to be longer only for users
who access specific pages which might take longer
to process, change it in code on those pages.
I'd only set the Session.Timeout to a longer value
in code in specific pages which take longer to process
( like long forms which the user has to fill in ).
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C8**********************************@microsof t.com... The question still is, say if you do want to chnage it from
the default value of 20 minutes, where is it best change it at?
"Juan T. Llibre" wrote:
The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com... > where do you suggest to set this at?
> I've heard in the web.config file:
> <sessionState mode="InProc" timeout="60">
> but I can't seem to get that to work?
> What about the global.asax file?
> I thought that page by page is over kill?
>
> thanx.
>
> "Ken Cox [Microsoft MVP]" wrote:
>
>> In code, it is Session.Timeout
>>
>> http://msdn.microsoft.com/library/de..._sesoptime.asp
>>
>> "Vishal" <an*******@discussions.microsoft.com> wrote in message
>> news:14****************************@phx.gbl...
>> > Hello,
>> >
>> > can anybody tell me how I can extend the session
>> > expiry time? Is it done via code or via IIS? Sorry I am
>> > new and dont know about this.
>> >
>> >
>>
>>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
so this statement should be correct, see prevoius thread:
<sessionState mode="InProc" timeout="60">
"Juan T. Llibre" wrote: That would depend on whether you want the
new value to be a globally applied value,
or whether you only want the session time
extended for users who access specific pages.
If you want the value applied globally, set it in web.config.
If you want the session to be longer only for users
who access specific pages which might take longer
to process, change it in code on those pages.
I'd only set the Session.Timeout to a longer value
in code in specific pages which take longer to process
( like long forms which the user has to fill in ).
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C8**********************************@microsof t.com... The question still is, say if you do want to chnage it from
the default value of 20 minutes, where is it best change it at?
"Juan T. Llibre" wrote:
The default value is a good figure : 20 minutes.
If you don't plan for your users to stay at any one
page without browsing to other pages for that
long, you could set it at 15 or even 10 minutes.
Setting it to a higher figure will only waste resources
if your users never stay at one page for as long a time
as you set in Session.Timeout.
Remember, Session_OnEnd only executes after
the number of minutes specified in Session.Timeout
has elapsed *without* the user having requested a page.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com...
> where do you suggest to set this at?
> I've heard in the web.config file:
> <sessionState mode="InProc" timeout="60">
> but I can't seem to get that to work?
> What about the global.asax file?
> I thought that page by page is over kill?
>
> thanx.
>
> "Ken Cox [Microsoft MVP]" wrote:
>
>> In code, it is Session.Timeout
>>
>> http://msdn.microsoft.com/library/de..._sesoptime.asp
>>
>> "Vishal" <an*******@discussions.microsoft.com> wrote in message
>> news:14****************************@phx.gbl...
>> > Hello,
>> >
>> > can anybody tell me how I can extend the session
>> > expiry time? Is it done via code or via IIS? Sorry I am
>> > new and dont know about this.
>> >
>> >
>>
>>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
Like I said before, globally setting the session timeout
to 60 minutes will cause higher resource consumption
( more ram consumption, for example ) than if you only
set the session.timeout to 60 minutes for those users
who have to stay a long time at specific pages.
Naturally, if *all* users have to go through a page which
takes an unusually long time to process, then setting the
session.timeout to a longer time makes sense, but if only
a subset of yours users need to spend that much time at
a single page ( without being able to request at least one
other page ), then setting the session.timeout to a larger
value will result in a waste of server resources.
The longer the session.timeout value,
the more resources are consumed by the server.
This becomes quite critical at servers which have a
large number of concurrent users within the time period
specified in web.config.
To give you an idea, if you have 100,000 user sessions
within one hour ( and you set session.timeout to 60 minutes )
and you store 10kb per user in the session object,
you will need 1GB RAM just to store session data.
If you store 100kb per user in the session object,
you'd need 10GB RAM, just to store session data.
If your site is a low-traffic site, then you can safely set
the session.timeout to 60 minutes, because it probably
won't matter ( unless you store 100MB per user in the
session object, heh, heh... )
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:D5**********************************@microsof t.com... so this statement should be correct, see prevoius thread:
<sessionState mode="InProc" timeout="60">
"Juan T. Llibre" wrote:
That would depend on whether you want the
new value to be a globally applied value,
or whether you only want the session time
extended for users who access specific pages.
If you want the value applied globally, set it in web.config.
If you want the session to be longer only for users
who access specific pages which might take longer
to process, change it in code on those pages.
I'd only set the Session.Timeout to a longer value
in code in specific pages which take longer to process
( like long forms which the user has to fill in ).
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C8**********************************@microsof t.com... > The question still is, say if you do want to chnage it from
> the default value of 20 minutes, where is it best change it at?
>
> "Juan T. Llibre" wrote:
>
>> The default value is a good figure : 20 minutes.
>>
>> If you don't plan for your users to stay at any one
>> page without browsing to other pages for that
>> long, you could set it at 15 or even 10 minutes.
>>
>> Setting it to a higher figure will only waste resources
>> if your users never stay at one page for as long a time
>> as you set in Session.Timeout.
>>
>> Remember, Session_OnEnd only executes after
>> the number of minutes specified in Session.Timeout
>> has elapsed *without* the user having requested a page.
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:9B**********************************@microsof t.com...
>> > where do you suggest to set this at?
>> > I've heard in the web.config file:
>> > <sessionState mode="InProc" timeout="60">
>> > but I can't seem to get that to work?
>> > What about the global.asax file?
>> > I thought that page by page is over kill?
>> >
>> > thanx.
>> >
>> > "Ken Cox [Microsoft MVP]" wrote:
>> >
>> >> In code, it is Session.Timeout
>> >>
>> >> http://msdn.microsoft.com/library/de..._sesoptime.asp
>> >>
>> >> "Vishal" <an*******@discussions.microsoft.com> wrote in message
>> >> news:14****************************@phx.gbl...
>> >> > Hello,
>> >> >
>> >> > can anybody tell me how I can extend the session
>> >> > expiry time? Is it done via code or via IIS? Sorry I am
>> >> > new and dont know about this.
>> >> >
>> >> >
>> >>
>> >>
>>
>>
>> ---
>> Outgoing mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
>>
>>
>>
In this case, this is a local web application, not open to the public. Users
are 25.
Another senerio that you didn't consider is the age old issue with users in
a corporate enviroment that like to "keep" their windows open at all times,
just in case they need to do something in that app. So sometimes we set the
timeout higher because they complain when they come back after lunch,etc and
are forced to log back in.
It's like trying to make a web app as close to client server as possible.
We're getting closer, but just not there.
Thanx.
"Juan T. Llibre" wrote: Like I said before, globally setting the session timeout
to 60 minutes will cause higher resource consumption
( more ram consumption, for example ) than if you only
set the session.timeout to 60 minutes for those users
who have to stay a long time at specific pages.
Naturally, if *all* users have to go through a page which
takes an unusually long time to process, then setting the
session.timeout to a longer time makes sense, but if only
a subset of yours users need to spend that much time at
a single page ( without being able to request at least one
other page ), then setting the session.timeout to a larger
value will result in a waste of server resources.
The longer the session.timeout value,
the more resources are consumed by the server.
This becomes quite critical at servers which have a
large number of concurrent users within the time period
specified in web.config.
To give you an idea, if you have 100,000 user sessions
within one hour ( and you set session.timeout to 60 minutes )
and you store 10kb per user in the session object,
you will need 1GB RAM just to store session data.
If you store 100kb per user in the session object,
you'd need 10GB RAM, just to store session data.
If your site is a low-traffic site, then you can safely set
the session.timeout to 60 minutes, because it probably
won't matter ( unless you store 100MB per user in the
session object, heh, heh... )
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:D5**********************************@microsof t.com... so this statement should be correct, see prevoius thread:
<sessionState mode="InProc" timeout="60">
"Juan T. Llibre" wrote:
That would depend on whether you want the
new value to be a globally applied value,
or whether you only want the session time
extended for users who access specific pages.
If you want the value applied globally, set it in web.config.
If you want the session to be longer only for users
who access specific pages which might take longer
to process, change it in code on those pages.
I'd only set the Session.Timeout to a longer value
in code in specific pages which take longer to process
( like long forms which the user has to fill in ).
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C8**********************************@microsof t.com...
> The question still is, say if you do want to chnage it from
> the default value of 20 minutes, where is it best change it at?
>
> "Juan T. Llibre" wrote:
>
>> The default value is a good figure : 20 minutes.
>>
>> If you don't plan for your users to stay at any one
>> page without browsing to other pages for that
>> long, you could set it at 15 or even 10 minutes.
>>
>> Setting it to a higher figure will only waste resources
>> if your users never stay at one page for as long a time
>> as you set in Session.Timeout.
>>
>> Remember, Session_OnEnd only executes after
>> the number of minutes specified in Session.Timeout
>> has elapsed *without* the user having requested a page.
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:9B**********************************@microsof t.com...
>> > where do you suggest to set this at?
>> > I've heard in the web.config file:
>> > <sessionState mode="InProc" timeout="60">
>> > but I can't seem to get that to work?
>> > What about the global.asax file?
>> > I thought that page by page is over kill?
>> >
>> > thanx.
>> >
>> > "Ken Cox [Microsoft MVP]" wrote:
>> >
>> >> In code, it is Session.Timeout
>> >>
>> >> http://msdn.microsoft.com/library/de..._sesoptime.asp
>> >>
>> >> "Vishal" <an*******@discussions.microsoft.com> wrote in message
>> >> news:14****************************@phx.gbl...
>> >> > Hello,
>> >> >
>> >> > can anybody tell me how I can extend the session
>> >> > expiry time? Is it done via code or via IIS? Sorry I am
>> >> > new and dont know about this.
>> >> >
>> >> >
>> >>
>> >>
>>
>>
>> ---
>> Outgoing mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
>>
>>
>>
With only 25 users, you can set the timeout
to 600 ( 10 hours ) without problems.
That will keep everybody within the same
session during normal working hours.
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A6**********************************@microsof t.com... In this case, this is a local web application, not open to the public.
Users
are 25.
Another senerio that you didn't consider is the age old issue with users
in
a corporate enviroment that like to "keep" their windows open at all
times,
just in case they need to do something in that app. So sometimes we set
the
timeout higher because they complain when they come back after lunch,etc
and
are forced to log back in.
It's like trying to make a web app as close to client server as possible.
We're getting closer, but just not there.
Thanx.
"Juan T. Llibre" wrote:
Like I said before, globally setting the session timeout
to 60 minutes will cause higher resource consumption
( more ram consumption, for example ) than if you only
set the session.timeout to 60 minutes for those users
who have to stay a long time at specific pages.
Naturally, if *all* users have to go through a page which
takes an unusually long time to process, then setting the
session.timeout to a longer time makes sense, but if only
a subset of yours users need to spend that much time at
a single page ( without being able to request at least one
other page ), then setting the session.timeout to a larger
value will result in a waste of server resources.
The longer the session.timeout value,
the more resources are consumed by the server.
This becomes quite critical at servers which have a
large number of concurrent users within the time period
specified in web.config.
To give you an idea, if you have 100,000 user sessions
within one hour ( and you set session.timeout to 60 minutes )
and you store 10kb per user in the session object,
you will need 1GB RAM just to store session data.
If you store 100kb per user in the session object,
you'd need 10GB RAM, just to store session data.
If your site is a low-traffic site, then you can safely set
the session.timeout to 60 minutes, because it probably
won't matter ( unless you store 100MB per user in the
session object, heh, heh... )
Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:D5**********************************@microsof t.com... > so this statement should be correct, see prevoius thread:
>
> <sessionState mode="InProc" timeout="60">
>
>
> "Juan T. Llibre" wrote:
>
>> That would depend on whether you want the
>> new value to be a globally applied value,
>> or whether you only want the session time
>> extended for users who access specific pages.
>>
>> If you want the value applied globally, set it in web.config.
>>
>> If you want the session to be longer only for users
>> who access specific pages which might take longer
>> to process, change it in code on those pages.
>>
>> I'd only set the Session.Timeout to a longer value
>> in code in specific pages which take longer to process
>> ( like long forms which the user has to fill in ).
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:C8**********************************@microsof t.com...
>> > The question still is, say if you do want to chnage it from
>> > the default value of 20 minutes, where is it best change it at?
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> The default value is a good figure : 20 minutes.
>> >>
>> >> If you don't plan for your users to stay at any one
>> >> page without browsing to other pages for that
>> >> long, you could set it at 15 or even 10 minutes.
>> >>
>> >> Setting it to a higher figure will only waste resources
>> >> if your users never stay at one page for as long a time
>> >> as you set in Session.Timeout.
>> >>
>> >> Remember, Session_OnEnd only executes after
>> >> the number of minutes specified in Session.Timeout
>> >> has elapsed *without* the user having requested a page.
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:9B**********************************@microsof t.com...
>> >> > where do you suggest to set this at?
>> >> > I've heard in the web.config file:
>> >> > <sessionState mode="InProc" timeout="60">
>> >> > but I can't seem to get that to work?
>> >> > What about the global.asax file?
>> >> > I thought that page by page is over kill?
>> >> >
>> >> > thanx.
>> >> >
>> >> > "Ken Cox [Microsoft MVP]" wrote:
>> >> >
>> >> >> In code, it is Session.Timeout
>> >> >>
>> >> >> http://msdn.microsoft.com/library/de..._sesoptime.asp
>> >> >>
>> >> >> "Vishal" <an*******@discussions.microsoft.com> wrote in message
>> >> >> news:14****************************@phx.gbl...
>> >> >> > Hello,
>> >> >> >
>> >> >> > can anybody tell me how I can extend the session
>> >> >> > expiry time? Is it done via code or via IIS? Sorry I am
>> >> >> > new and dont know about this.
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >>
>> >>
>> >> ---
>> >> Outgoing mail is certified Virus Free.
>> >> Checked by AVG anti-virus system (http://www.grisoft.com).
>> >> Version: 6.0.794 / Virus Database: 538 - Release Date: 10/11/2004
>> >>
>> >>
>> >>
>>
>>
>>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Christophe Lance |
last post by:
Hello,
I use PHP session cookie to store an id number.
I know how to set a cookie expiration date using the setcookie function, but
how to set an expiration date when the cookie is created by...
|
by: Craig Storey |
last post by:
I have a form where users logged in using sessions can edit articles in
a WYSIWYG editor. Some of them take their time and don't like to save
their work very often and occassionally the sessions...
|
by: Igor |
last post by:
Is it possible to point current context's session to another active
session based on a SessionID?
|
by: VB Programmer |
last post by:
I know you can make cookies expire, but how about session variables? I'm
basically using session for security, etc... One variable is
session("LoggedOn"). If a page sits idle for 30 minuts I...
|
by: ChrisN |
last post by:
Hi there,
Two questions related to each other.
1. Session variables expire by defualt when not used for 20 minutes. Does
"used" mean that a user has not access any session varibles in 20...
|
by: jensen bredal |
last post by:
Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be...
|
by: spacehopper_man |
last post by:
I'm considering ditching all use of Session state in favour of
Application state.
This is because - from what I can work out - it will be more memory
efficient for me.
I have three questions:...
|
by: Riaan |
last post by:
Hi guys!
I have an issue that needs urgent resolution. Imagine this scenario:
You have:
1 production server running Windows Server 2003, IIS6 and an instance
of MSDE 2000.
There is an...
|
by: Goofy |
last post by:
Does anyone know how I can kill a session by session ID ?
--
Goofy
|
by: sb5309 |
last post by:
When one uses CAPTCHA (form with verification code), a session is
required to keep the session data.
In examples that I have seen on the net, I did not see a session is
closed after use.
...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
| |
