Springside Development Combat (vi): AJAX, walking in the hell

Speaking of Ajax, everyone is not unfamiliar, after all, these two years it is too popular. However, where Ajax is really needed, not everyone can handle it well. Using AJAX, you can develop a luxurious browser-based rich client interface, but the sheer size of the development and the difficulty of debugging make every programmer a life of hell.

I think there are two things that really need Ajax:

1, the user does not want his attention to the information out of his sight. For example, when filling out some forms, sometimes hard to fill out something, a little submit button, all gone, if a field validation failed, then all the things to be filled from scratch, really let people depressed. Although the design of a better site can retain the information that users fill out, but in the page after the submission of the Flash, users still have a sense of unease.

2, users do not want a small update to refresh the entire huge page. For example, users reply to a very long and full of pictures of the article, although the content of the reply only a few words, but to wait for the long page refresh, but also create a bad user experience.

If I use Ajax simply to achieve a gorgeous effect, I personally think it is not.

Based on the above summary, I would like to implement the function of such a registered user, to allow users to submit information does not need to refresh the page, all the field validation is sent back to the server side, verify the error message to the form page, the entire process does not refresh the page, know that after the successful registration jump to the first page, the following figure:

1, for users to fill out the form

2, after the user fills in the information, the form becomes not editable, and prompts the data is submitting