外文翻译3 Ajax and the Server-Side Technologies.docVIP

外文原文 来源： 《Mastering Ajax》 14 Aug 2007 From OReilly Media Inc. 3 Ajax and the Server-Side Technologies Thus far, this book has already established that the major difference between the way server-side technologies normally work (the “add data-send-wait” model) and the way in which Ajax works (by calling the server asynchronously) is the primary way in which Ajax alters the traditional pattern of web page usage. Ajax isn’t restricted to just one pattern of usage, and in Chapter 9 you will see how there are varying patterns by which Ajax can alter the flow of data from the client to the server. The one similarity all these patterns share is that you are no longer tied to having to explicitly submit a form and then wait for its response. Let’s talk a little about how forms and HTML controls are used in the page. Forms and HTML Controls Ajax doesn’t alter the fundamental way in which HTML controls work and the way in which data is retrieved from them. You still have a set of HTML controls (such as drop-down lists, radio buttons, check boxes, text boxes, and text areas), and these are still submitted to the server. The server picks them up in the same way. There are two big changes, however. The first is the way in which the server-side page is called, and the second is the fact that the HTML form can be completely removed from the page or doctored to such an extent that it doesn’t work in the expected way. Let’s explain this by first taking a closer look at how the existing model of submitting a form to the server side works. The Forms Model of Submission With any server-side technology, the normal way of submitting a form is to have a form with a button that is submitted to the server when the user clicks the button. Classic ASP and PHP would use the form’s ACTION attribute to redirect the user from an original page to a response page. The processing is done on the server before the user is redirected to a new page, and the new page is used to display the data (F