Remote Scripting Advanced Tutorial---using remote scripting

Overview
With remote scripting, developers can now create seamless (seamless), interactive Web applications in which browsers can invoke scripts on the server without reloading the Web page.
Prior to remote scripting, in order to interact with the server, the developer had to require the user to reload the called page and often load it multiple times. This causes the server to use slow, inconsistent, user experience and low efficiency.
Remote scripting makes it possible to have more client/server type interactions between browsers and WEB servers. For example, when you fill out a table on a Web page, the user must reload the entire page often, multiple times, before the application validates the entry. Remote Scripting,web applications can now validate data while the user is still populating the rest of the table without reloading the page. Specifically, the script must first confirm the server page to which you want to connect before transferring the call to the server. Any return value from the call is passed back to the original script.
Using Remote scripting
Remote scripting users in WEB applications have the ability to integrate two scripting platforms into a single home page. Users can create client scripts to control the user interface of the application and, if they are using Microsoft Internet Explorer 4.0, can also take advantage of the power of Dynamic HTML (DHTML). At the same time, users can run scripts on their own servers to perform server-side tasks, including database queries, middle-tier business logic, and so on. Since the client page is still active, the remote scripting is running on the server, so the user script is greatly simplified and the application can display a richer, more responsive user interface.