s for network resources. The client side display (browser) environment provides the front end to an application. In this environment, for example, you display HTML pages in windows and maintain browser session histories of HTML pages displayed during a session. The objects in this environment must be able to manipulate pages, windows, and histories. On the other hand, in the server environment you work with the resources on the server. For example, you can connect to relational databases, share information across users of an application, or manipulate the server's file system. The objects in this environment must be able to manipulate relational databases and server file systems. In addition, an HTML page is not displayed on the server. It is retrieved from the server to be displayed on the client. The page retrieved can contain client-side JavaScript. If the requested page is part of a JavaScript application, the server may generate this page on the fly. Servers and clients have many dissimilar capabilities such as:Servers Usually (though not always) high-performance workstations with fast processors and large storage capacities.Can become overloaded when accessed by thousands of clients.ClientsAre often desktop systems with less processor power and storage capacity.Are often single-user machines, so it can be advantageous to offload processing to the client.Preprocessing data on the client can also reduce bandwidth requirements, if the client application can aggregate data.In conclusion, there are usually a variety of ways to partition an application between client and server. Some tasks can be performed only on the client or on the server; others can be performed on either.Use client processing (the SCRIPT tag) for these tasks: 1.Validating user input; that is, checking that values entered in forms are valid 2.Prompting a user for confirmation and displaying error or informational dialog boxes 3.Performing aggregate calculations (suc...
