What is Stateless in MVC

Question

0.00/5 (No votes)

See more:

Hello,

I had read that MVC is stateless.
Now i found the meaning of stateless that, If the user requests the same page again, the server repeats the entire sequence, reprocessing the page from scratch. Put another way, a server has no memory of pages that it has processed—page are stateless. Therefore, if an application needs to maintain information about a page.

but still i am confused. Not getting idea.
If MVC is stateless then session variable is not available in MVC?
Or session variable and stateless is different?

Thanks,
Viprat

Posted 8-Jan-13 1:07am

VIPR@T

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2013-01-08T01:19:00

Http is stateless by definition.
Even if classic asp.net claims to be statefull, it is simulating state by storing some state information and sending it from client to server and back. Actually the IIS + ASP.NET processing pipeline is more complicated to declare it statefull or stateless, since there are application objects that persist between several calls. But this is highly configurable and depends on many things.

Session is of course there in MVC also, and that's the primary storage of volatile data to be passed between calls, that we don't want to persist.

Believe me, the MVC approach is the canonical one, the ASP.NET classic approach was an interesting but very unique approach.

If you want to get an insight in ASP.NET pipeline check this article: http://www.west-wind.com/presentations/howaspnetworks/howaspnetworks.asp[^]

puskar gupta · Answer 2 · 2013-01-08T01:18:00

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

[Moved From 2nd answer]
They are stateless in the sense that you can never know when the user stops using your site or that the session is lost if the browser fails to transport your state parameters. Compare with FTP or IRC. They have built in session support. Try maintaining state without cookies. It's possible but ugly (the user can just remove any query string parameter or the viewstate from the POST). It's still valid HTTP, but the session will be lost

What is Stateless in MVC

2 solutions

Solution 3

Solution 2

Add your solution here

Preview 0