What are some scenario's of having a Session-less Controller in ASP.NET MVC3?
Reading Guru-Gu's blog post about ASP.NET MVC3 hitting RC , he says:- Session-less Controller Support You can now indicate whether you want a Controller class to use session-state – and if so whether you want it to be read/write or readonly.read/write or readonly. Can someone explain what are some scenario's someone might want to have a session-less controller? or a read-only controller? I've always been creating a separate IIS website which I use to handle all static images/content and then have this same website have session state turned off ... so no cookies are sent over the wire. Is this