ASP.Net & Sessions Question

[Guest]

Hi all friends:

It's said that Sessions objects in ASP 3.0 with IIS 5.0 occupy certain memory of the machine which take to take care about use a lot of Sessions objects in the ASPs pages of the applications.

So my question is about how recommendable is to use a lot of Sessions objects in ASP.Net I want to use in my application 30 of this objects. Im gonna use them for give permissions to the users of the application.

Regards.

 

[Guest]

It really depends on your requirements. Performance? Scalability? etc. I recommend that you read the section in the .NET Framework SDK documentation about session management

Tu-Thac

----- Miguel wrote: ----

Hi all friends

It's said that Sessions objects in ASP 3.0 with IIS 5.0 occupy certain memory of the machine which take to take care about use a lot of Sessions objects in the ASPs pages of the applications

So my question is about how recommendable is to use a lot of Sessions objects in ASP.Net I want to use in my application 30 of this objects. Im gonna use them for give permissions to the users of the application

Regards

 

[Hermit Dave]

couldnt exactly get your question but i will try and give you an idea on how
to store objects

1. Application: you can store objects in application if you want to share it
between users. That was the way ASP 2.0 and 3.0 gave you the option.
With ASP.NET the worker process is bounced if it exceeds 60% of the
physical memory and if you start adding objects it might initiate the
bouncing.

2. Cache: This is the place to store all your global information Cache is a
smart object. When you insert an object in Cache... you set up the priority
and callbacks if any (if a method you need to explicitly call if the object
is unloaded from the memory). You can also set things like absolute
expiration and sliding expiration. If the cache is filled up and you try and
insert an object or if application memory usuage goes up... the objects in
cache as cleared based on their priority (callback functions if any will be
called)

3. Session objects: This is where you store user specific data. ie if each
user has data which is not common you user session to store the object

Hope this are clear....

--

Regards,

HD

Hi all friends:

It's said that Sessions objects in ASP 3.0 with IIS 5.0 occupy certain

memory of the machine which take to take care about use a lot of Sessions
objects in the ASPs pages of the applications.

So my question is about how recommendable is to use a lot of Sessions

objects in ASP.Net I want to use in my application 30 of this objects. Im
gonna use them for give permissions to the users of the application.

 

[Cowboy \(Gregory A. Beamer\)]

Session objects are not as bad under ASP.NET, but I would not use it as a
primary means of semi-persistant storage. 30 different values is a bit
overboard, but not terribly. 30 different objects per user could be postal.
Look at what you are trying to accomplish before making a decision. If the
data is eventually saved off, a temporary storage location (other database
tables) might be preferable if most people save this data off.

Without understanding your app, I can only be general about design.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************

Hi all friends:

It's said that Sessions objects in ASP 3.0 with IIS 5.0 occupy certain

memory of the machine which take to take care about use a lot of Sessions
objects in the ASPs pages of the applications.

So my question is about how recommendable is to use a lot of Sessions

objects in ASP.Net I want to use in my application 30 of this objects. Im
gonna use them for give permissions to the users of the application.