We have a web application running on classic ASP, where the session is
maintained in the Oracle DB, so every page redirect/form submit can
switch servers without any problem
we are looking now at writing a .NET application on the farm using same
Database. a couple of questions/notes:
- I understand you have to use "your own session provider" if you are
using non-SQL server. What exactly does it mean? Is there a standard
process that is executed automatically by .NET, and that we have to
implement using some established interface, or is it simply saying
"build some kind of code that will execute on every page, that will
set/retrieve the session in the Database?" if the former, where can I
find information on how to do it? if the latter, this is what we do
today anyway!
- Another issue is the "view state". is it true that if I set the code
to be constant, and not machine-dependant, then every post-back will be
OK even if redirected to another web server ? is that set on
machine.config level?
- for deployment, do we have to copy the same project to very web
server individually? is there a way to deploy to the farm in one go? or
a toll, that will replicate from one server to the others?
