dwr3 reverse ajax学习小结（dwr3反向Ajax学习小结）.docVIP

dwr3 reverse ajax学习小结（dwr3反向Ajax学习小结） In accordance with the example of the official website, and build their own examples of Clock, back to sum up the problems encountered: 1, piggyback way DWR uses the passive mode of piggyback by default, and does not require any additional configuration if it is needed. The so-called Piggyback refers to the background if what needs to be pushed to the foreground (i.e. JS method call page), is to wait until the page next time Ajax request, will need to push the contents of additional after the request back to the page. This method can replace the Ajax mode I used Jquery and so on. 2, polling way The browser sends the Ajax request to the server periodically, asking if there is any content in the background that needs to be pushed, and if anything, the server will return the push content. This approach is similar to the implementation of the Ajax request that we send directly through the page through the timer, and then query the background for changes. Similar to the Ajax polling mode, but after using the DWR, this part of the work done by the framework to help us. 3, comet mode Refers to when the server establishes the connection to the browser and sends the contents of the page to the browser, and the corresponding connection is not closed but only temporarily suspended. If there is something new behind it that needs to be pushed to the client, the data is transferred directly through the pending hang up connection. Now that you have the comet schema, I dont have to think about the polling method at all. The emphasis is on the comet model, that is, push mode. In the example of the official website, 3 are used, as follows: In the Clock instance Java code Public, void, setClockDisplay (final, String, output) { String page = ServerContextFactory.get ().GetContextPath () + /clock.html; Browser.withPage (page, new, Runnable () { Public, void, run () { Util.setValue (clockDisplay, output); } }); } For the page here, at first I set up