W
wardy
I've got a .NET web application that currently uses session to
maintain state. I am just looking down the road and thinking of
scaleability and if I need to go to a web farm, then using "inproc"
for managing my session will no longer work. I've done some research
and read about how SQL Server can manage session, but I've found very
little in terms of how to actually do this. Basically what I've found
so far is that I run a script that comes with .NET (can't think of the
name right now ) which sets up the tables and stored procs required
to manage the sessions. My question is once this is done, how is it
actually implemented? Are any code changes required (from the
"Session.Add" and "Session.Item" used with inproc session management)?
Thanks.
maintain state. I am just looking down the road and thinking of
scaleability and if I need to go to a web farm, then using "inproc"
for managing my session will no longer work. I've done some research
and read about how SQL Server can manage session, but I've found very
little in terms of how to actually do this. Basically what I've found
so far is that I run a script that comes with .NET (can't think of the
name right now ) which sets up the tables and stored procs required
to manage the sessions. My question is once this is done, how is it
actually implemented? Are any code changes required (from the
"Session.Add" and "Session.Item" used with inproc session management)?
Thanks.