Dear all

I would like to ask about session in asp.net(C#). In my new project I am using many sub domain by category. I want to control session state between each domains. Can I? plz help me?

 thz all
 

For State Server

<sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:55455" sqlConnectionString="data source=127.0.0.1;user id=sa;password='' cookieless="false" timeout="20"/>

The attributes are self explanatory but I will go over them.

mode: This can be StateServer or SqlServer. Since we are using StateServer we set the mode to StateServer.

stateConnectionString: connectionString that is used to locate the State Service. 

sqlConnectionString: The connection String of the sql server database.

cookieless: Cookieless equal to false means that we will be using cookies to store the session on the client side.

For SQL Server

<sessionState mode = "SqlServer" stateConnectionString="tcpip=127.0.0.1:45565"

sqlConnectionString="data source="SERVERNAME;user id=sa;password='' cookiesless="false" timeout="20"/>

 Hello,

Session in ASP.net can be stored in 3 ways.
1. Inproc
2. State Server
3. SqlServer


The InProc mode of Session State management is the fastest among all of the storage modes available and stores the Session data in the ASP.NET worker process.
Performance will be effected if the amount of data stored in the session is large. Basically the session is stored in the memory space of an application
domain and is volatile.So if asp.net worker process i.e. aspnet_wp.exe restarts then the session state will be lost.
The Session State here entirely depends on the lifetime of the application domain that it runs on. Note that the Session_End event which is fired internally by the web server is supported only in InProc mode. Note that even if the Session State is set to read only using the EnableSessionState attribute, in the InProc mode one can still modify the session. The Session_OnEnd event is invoked by the runtime environment when we make a call to the Session.Abandon() method or when the user's session times out. Further, any change made in the settings in the web.config file unloads the application domain and the Session State too.


The StateServer mode uses a stand-alone Microsoft Windows service that is independent of IIS and can run on a separate server.
In this case the session state is serialized and stored in memory in a separate process that is managed by the aspnet_state.exe file.
This has got some performance drawbacks due to the overhead involved in serialization and de-serialization of objects.
The main primary advantage of storing the Session State in a State Server is that it is not in the same process as the ASP.NET and a crash of ASP.NET
would in no way destroy the session data. Secondly, this mode of Session State storage enables to share the information across a web garden or a web farm.

Rememeber that this mode is slow compared to the InProc mode as it is stored in an external process.

The SQLServer mode of Session State management is a reliable, secure and centralized storage of a session state
In this the Session data is serialized and stored in a database table in the SQL Server database.
It can typically be used in the web farms.

It has performance bottlenecks as in the State Server mode of Session State management due to the overhead involved in serialization and de-serialization
of the objects that are stored and retrieved to and from the Session.
SQL Server is more secure than the InProc or the State server modes of Session State storages as the data can be secured easily by
configuring the SQL Server security. 

I hope this will helps you out..

With Regards..

Ashish Shah

India

NOTE:: PLease mark this post as answered if you like / post is useful to you... 

niharnayak2003:

For SQl Server 

For State Server

<sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:55455" sqlConnectionString="data source=127.0.0.1;user id=sa;password='' cookieless="false" timeout="20"/>

For SQL Server

<sessionState mode = "SqlServer" stateConnectionString="tcpip=127.0.0.1:45565"

sqlConnectionString="data source="SERVERNAME;user id=sa;password='' cookiesless="false" timeout="20"/>

Dear bro...

Plz let me know. My project have using many web application. So, do I need to write this SessionState any web.config file from every application and were can I write this in web.config.

Hello,

Please visit the links below:

http://www.csharphelp.com/archives/archive207.html

http://www.eggheadcafe.com/articles/20021016.asp

http://www.codeproject.com/KB/aspnet/SessionManagementAspNet.aspx

http://www.programmersheaven.com/2/State-Management-in-ASP-NET

If I'm not wrong, you're trying to share the session across multiple ASP.NET applications.

Here's how you do it...

1) Use SQL Server for storing session state.

2) Tweak "TempGetAppID" in the session database so that it returns session values for multiple applications  - refer to the below link to achieve this.

http://blogs.msdn.com/toddca/archive/2007/01/25/sharing-asp-net-session-state-across-applications.aspx

Hope this helps.

 hi,

how did you manage the serialization using vb? im not using class but function... any ideas? thanks a lot... 

im not using c#....