Is ASP.NET MVC stateless? [closed]

Answer 1

MVC is not (totally) stateless. No web framework is.

I think this refers to the fact that MVC abolishes the _VIEWSTATE field.

But do provide a link or more information.

Answer 2

State is managed in ASP.NET (MVC and WebForms) through several means:

• Session
• Cookies
• Form posts
• Application
• Query string
• Cache
• Context

MVC eliminates ViewState, which means that controls (text boxes, checkboxes, etc.) lose their values each time a page is posted back. You need to repopulate them manually or through other means (Model binding, for instance).

MVC isn't truly stateless, but it does remove one of the most common ways of persisting state in ASP.NET -- the ViewState.

Answer 3

the web is stateless, therefore anything built on top of http is stateless. by stateless I mean each request/response is an atomic unit with no knowledge of any previous request.

there are mechanisms with http that allow you to hold some form of state between requests like Session and Application, but generally, these should be used as little as possible.

Webforms attempts to create the illusion of state by introducing ViewState and Postback. But this doesn't change the fact that the web is stateless.

Answer 4

I would say all web communication is stateless except some of the new technologies like SignalR [Async signaling library for ASP.NET to help build real-time, multi-user interactive web applications] .

You make a request and get a response, that is it, perhaps what you are thinking of is not using ViewState like in webforms.

Answer 5

MVC is stateless because HTTP is. There is nothing in HTTP that indicates when a session starts or ends.

Every web framework tries to overcome this by using either a cookie or Request/Response features like the query string or FORM post.