What are the implications on Application and Session state variables in a web farm or a web garden?-tech10032012

In both a Web garden and a Web farm, client requests are directed to the ASP.NET process that is currently least busy. That means that a single client can interact with different CPUs or servers over the course of his or her session. This has the following implications for Application and Session state variables: Application state variables are unique to each separate instance of the Web application. Clients can share information through Application state if the Web application is running on a Web garden or a Web farm. Session state variables are stored in-process by default. To enable Session state in a Web garden or Web farm, you need to specify a Session state provider.