Session variable question

The multi-server issue is true. You'll have to serialize the session object and stash it in a db. Use querystring/get to pass your own unigue session ID/DB key as part of each uri within the site. I seem to recall some pretty good examples of this on www.asp.net and in the mskb.

You'll also have some cert issues if you're using ssl. May need a different type of cert.

dpyers wrote: The multi-server issue is true. You'll have to serialize the session object and stash it in a db. Use querystring/get to pass your own unigue session ID/DB key as part of each uri within the site. I seem to recall some pretty good examples of this on www.asp.net and in the mskb. You'll also have some cert issues if you're using ssl. May need a different type of cert.

I don't believe you'll have to make any coding changes at all.

All you need to do is change the location where session info is stored.  You can do this in your web.config.

From memory, there are 3 options - memory (in process), database and one other which I've forgotten. 

This should get around your server-farm issue.

Cheers,
Andrew

EDIT: The other is out of process (state server).  See:
http://www.ondotnet.com/pub/a/dotnet/2003/03/24/sessionstate .html