Use Asp.net MVC to develop applications. Is page. ispostback useful on the page?

I have been studying Asp.net MVC for a while, and I have also used Asp.net MVC to develop two sets of applications.Program, Although it is not a big system.

I also want to raise a special question today. I don't know if I don't know, or it is difficult to implement attributes such as ispostback in page in Asp.net MVC, at present, Asp.net MVC has lost its role, so that some of their own one-time binding or value assignment do not need to obtain data in the next time, but now all need to obtain data again. The data won't be retrieved again after a refresh (especially from the database), and now it will be read again, I wonder if Asp.net MVC determines in action whether the second request of the same context does not need to refresh the entire page?

Let's take a look at the effect. Check the current page

 

Refresh the page. If I still need to obtain some data from the database on the page, this will actually affect the performance.

I also know that Asp.net MVC does not provide good support for server control functions. For example, some automatic backhaul and server event models cannot be used, (Some events that can be loaded with server controls for the first time, such as repeater binding events ), it can be said that the control events that can respond to server events as long as there is a callback are no longer available. Data Controls can only display data and data layout. Of course, there are some open-source helper classes in the Asp.net MVC framework, which can help us a lot. However, it is time to use Asp.net MVC for development. Many times, I think that ASP is used for development. Many serversCodeMany of them will be nested in HTML code, which seems messy. Of course, I am not saying that Asp.net MVC framework development applications will not be good. Asp.net MVC and Asp.net webform have their respective advantages. We can't beat everyone to death, but I just want to discuss this issue with everyone's thinking. In a broad sense, ji si studies and learns together.

In fact, Asp.net webform also has some excellent design methods. I don't know if Asp.net MVC has taken into account the excellent design before Asp.net. If you can determine whether the same request is in the action, and then do not need to regenerate a view, it can also reduce the pressure on the server to refresh. Ispostpack is really useful for us, and it is impossible to prevent others from refreshing constantly. It's not long before I enter the course, and the technology is very good. If Daniel knows the problem of this method or has a good solution to the performance of Asp.net MVC development, you can introduce them to me. I am very loyal to the technology. I would like to thank you for your introduction.