Application Variable

[Lord2702]

I have 20 - 25 users using my web application, and I store their UserID,
along with their SessionID in Aplications Variable. Now, My question is,
suppose if my users increase to 100, 1000, or even 10,000 then still this
system will work w/o having any memory problem ? Ofcourse when user has Log
Off, then I remove it from these arrays, but still it is possible that at a
time 1000 users may be login at a time.

Tia

[Hermit Dave]

i dont see any problems to your approach though i am just wondering.... what
happens if the user just closes the browser without going into the effort of
clicking the Logout button ?
Memory issues if any will be determined by what exact information you are
storing per user in the application object. if you are storing large amounts
of user specific data then you need to use a different approach

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Lord2702" <Lo******@MSN.com> wrote in message
news:uE*************@tk2msftngp13.phx.gbl...

I have 20 - 25 users using my web application, and I store their UserID,
along with their SessionID in Aplications Variable. Now, My question is,
suppose if my users increase to 100, 1000, or even 10,000 then still this
system will work w/o having any memory problem ? Ofcourse when user has Log Off, then I remove it from these arrays, but still it is possible that at a time 1000 users may be login at a time.

Tia

[Hans Kesting]

Lord2702 wrote:

I have 20 - 25 users using my web application, and I store their
UserID, along with their SessionID in Aplications Variable. Now, My
question is, suppose if my users increase to 100, 1000, or even
10,000 then still this system will work w/o having any memory problem
? Ofcourse when user has Log Off, then I remove it from these arrays,
but still it is possible that at a time 1000 users may be login at a
time.

Tia

Are you using Lock/Unlock when you change those stored values?
This might slow your application down when there are a lot of users.

Hans Kesting

[Scott Allen]

Hermit Dave has a good point. It really depends on what you are
storing per user, how much RAM is on the machine, and lots of other
factors. The only way to know exactly what will happen is to give the
application a stress test.

What version of Visual Studio are you using? You might have ACT
installed.
http://msdn.microsoft.com/library/de...nethowto10.asp

--
Scott
http://www.OdeToCode.com/

On Thu, 7 Oct 2004 06:02:54 +0100, "Hermit Dave"
<he************@CAPS.AND.DOTS.hotmail.com> wrote:

i dont see any problems to your approach though i am just wondering.... what
happens if the user just closes the browser without going into the effort of
clicking the Logout button ?
Memory issues if any will be determined by what exact information you are
storing per user in the application object. if you are storing large amounts
of user specific data then you need to use a different approach

[Lord2702]

My storage could be maximum 16 - 20 bytes per user, and I can shorten it
upto 8 bytes. But as Hermit mention if user close the browser w/o clicking
on Logout then How should I handle this situation ? And, what could be the
best approach to store the Login user information in ASP.Net application ? I
appreciate your reply.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:8t********************************@4ax.com...

Hermit Dave has a good point. It really depends on what you are
storing per user, how much RAM is on the machine, and lots of other
factors. The only way to know exactly what will happen is to give the
application a stress test.

What version of Visual Studio are you using? You might have ACT
installed.
http://msdn.microsoft.com/library/de...nethowto10.asp
--
Scott
http://www.OdeToCode.com/

On Thu, 7 Oct 2004 06:02:54 +0100, "Hermit Dave"
<he************@CAPS.AND.DOTS.hotmail.com> wrote:

i dont see any problems to your approach though i am just wondering.... whathappens if the user just closes the browser without going into the effort ofclicking the Logout button ?
Memory issues if any will be determined by what exact information you are
storing per user in the application object. if you are storing large amountsof user specific data then you need to use a different approach

[Scott Allen]

16-20 bytes is a relatively small amount, so I would not see any
problems there. When the user closes the browser without signing out,
you'll just have to wait for the runtime to clean up unused sessions,
there is no method for your code to call and speed up that process.

--
Scott
http://www.OdeToCode.com/

On Thu, 7 Oct 2004 12:12:32 -0700, "Lord2702" <Lo******@MSN.com>
wrote:

My storage could be maximum 16 - 20 bytes per user, and I can shorten it
upto 8 bytes. But as Hermit mention if user close the browser w/o clicking
on Logout then How should I handle this situation ? And, what could be the
best approach to store the Login user information in ASP.Net application ? I
appreciate your reply.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:8t********************************@4ax.com.. .

Hermit Dave has a good point. It really depends on what you are
storing per user, how much RAM is on the machine, and lots of other
factors. The only way to know exactly what will happen is to give the
application a stress test.

What version of Visual Studio are you using? You might have ACT
installed.

http://msdn.microsoft.com/library/de...nethowto10.asp

--
Scott
http://www.OdeToCode.com/

On Thu, 7 Oct 2004 06:02:54 +0100, "Hermit Dave"
<he************@CAPS.AND.DOTS.hotmail.com> wrote:

>i dont see any problems to your approach though i am just wondering....what >happens if the user just closes the browser without going into the effortof >clicking the Logout button ?
>Memory issues if any will be determined by what exact information you are
>storing per user in the application object. if you are storing largeamounts >of user specific data then you need to use a different approach

[Hermit Dave]

well is it essential that you store that info in Application object ?

I have had scenarios where i had to store session id and the current sorting
criteria but it was very specific requirement for a very specific user group
on a server that i had control over :). Infact given the option i would have
preferred to think of a different approach if i had sufficient time.

what i would suggest is using a database table and storing the info there.
plus you can store like log in time and last access time etc. schedule a sql
job to run every now and again say half an hour or an hour and clean up if
no activity has been registered from user

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Lord2702" <Lo******@MSN.com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl...

My storage could be maximum 16 - 20 bytes per user, and I can shorten it
upto 8 bytes. But as Hermit mention if user close the browser w/o clicking
on Logout then How should I handle this situation ? And, what could be the
best approach to store the Login user information in ASP.Net application ? I appreciate your reply.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:8t********************************@4ax.com...

Hermit Dave has a good point. It really depends on what you are
storing per user, how much RAM is on the machine, and lots of other
factors. The only way to know exactly what will happen is to give the
application a stress test.

What version of Visual Studio are you using? You might have ACT
installed.

http://msdn.microsoft.com/library/de...nethowto10.asp

--
Scott
http://www.OdeToCode.com/

On Thu, 7 Oct 2004 06:02:54 +0100, "Hermit Dave"
<he************@CAPS.AND.DOTS.hotmail.com> wrote:

i dont see any problems to your approach though i am just wondering.... whathappens if the user just closes the browser without going into the effort of

clicking the Logout button ?
Memory issues if any will be determined by what exact information you

arestoring per user in the application object. if you are storing large

amountsof user specific data then you need to use a different approach