Q
quique
Hi all,
I want to know the advantages and disadvantages of the
methods of maintain session state, obviously if i choose
sqlserver is the most robust but the less performace..
If wan't to maintain session state in sqlserver, Does
anybody knows when it's saved to database?, on
beguinSession, on endSession...
<sessionState
mode="SQLServer"
stateConnectionString="tcpip=127.0.0.1:500"
sqlConnectionString="data
source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/>
If i want to mantain session state in ServerState (it
maintains in memory) if the machine that is listening
fails (in the example below is listening in the port
500), can i access to session state ??
<sessionState
mode="StateServer"
stateConnectionString="tcpip=127.0.0.1:500"
sqlConnectionString="data
source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/>
Any ideas apreciated
Thanks
I want to know the advantages and disadvantages of the
methods of maintain session state, obviously if i choose
sqlserver is the most robust but the less performace..
If wan't to maintain session state in sqlserver, Does
anybody knows when it's saved to database?, on
beguinSession, on endSession...
<sessionState
mode="SQLServer"
stateConnectionString="tcpip=127.0.0.1:500"
sqlConnectionString="data
source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/>
If i want to mantain session state in ServerState (it
maintains in memory) if the machine that is listening
fails (in the example below is listening in the port
500), can i access to session state ??
<sessionState
mode="StateServer"
stateConnectionString="tcpip=127.0.0.1:500"
sqlConnectionString="data
source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/>
Any ideas apreciated
Thanks