I also understand that IIS does not scale objects across multiple IIS servers, is that correct? If so...and you have a 3-server IIS farm, if someone comes in on server 2 and creates an object (or just a simple session variable), their next connection to the IIS farm could be on server 1...where the object doesn't already exist?

Yet another reason to maintain states with a database or something like that.

-Joe


>It's primarily a scalability thing. Always remember that the Session object and the variables and objects it contain are stored on the web server. This means that for every user, you could have one of those objects instantianted. Multiply the resources used by that object by the number of users and the resource usage on the server can skyrocket. Add more objects and it gets even worse. We rarely store anything to the session object for that reason. Sure it's convenient, but if a site starts to get heavy traffic, it can cause you serious grief.