Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using ASP.NET MVC application. However I am not able to understand the fact that in ASP.NET MVC pages are not posted/no postbacks. How is that possible? Unless posting the data how can the MVC framework manipulate the posted data. So what is the point in telling ASP.NET MVC does not have post backs. And also what the REST principle all about?
Not able to understand from the web contents I have seen. Can anyone explain?
The difference between ASP.NET posts and ASP.NET MVC posts is that in MVC, your page does not undergo the traditional page lifecycle of ASP.NET. Instead, your posts are mapped to a single method for processing.
Part of the appeal of MVC is that it divorces itself from some of the state-tracking mechanisms of traditional ASP.NET. Since each POST or GET is mapped to an individual controller and method, it becomes less necessary to track things like view state.
By not posting back as much state information and processing a full page lifecycle, the post model is rightly considered characteristically different from traditional web forms, but still relies on the HTTP methods we are familiar with.
With respect to your question about REST, you can read a high-level overview on Wikipedia: http://en.wikipedia.org/wiki/Representational_State_Transfer