Coldfusion Web Hosting - Java Programming - Cheap Web Hosting Blog

CHAPTER 10 INFINITE DATA PATTERN
No Result

The HTML page implementation, like previous pattern implementations, includes a number of JavaScript files referenced by using the script HTML tag. Unlike previous patterns, on the client side the Infinite Data pattern does not reference any script files that implement a generic Infinite Data infrastructure. There is no Infinite Data infrastructure; the activity diagram illustrated in Figure 10-1 shows that all of the logic is application specific. The Infinite Data pattern does instantiate the ClientCommunicator type that is an implementation of the Persistent Communications pattern. The instantiated Persistent Communications pattern is assigned to the variable client, and the property baseURL is assigned to the file /ajax/ chap08/PrimeNumberHandler.aspx. The file /ajax/chap08/PrimeNumberHandler.aspx represents the server-side implementation of the Infinite Data pattern. The HTML page contains the HTML element table that contains four rows used to send and receive the Infinite Data state. When the buttons that have the onclick event handlers defined as SendData1or SendData2 are clicked, the structure is assembled and sent for processing to the server. The sent structure is stored in the input elements with the identifiers number1 and number2. When the result structures are received, they are processed and inserted into the span elements with the identifiers result1 and result2. Defining the Sending and Receiving Contract Before further illustrating the code on the client and server sides, the contract between the two sides needs to be defined. The contract in an Ajax application is the data that is sent between the client and the server. In the Infinite Data pattern implementation, there are two contracts: what the client sends as a structure to be processed by the server, and the result structures sent by the server and processed by the client. The state for the structure is stored in the HTML form inputfields, which happen to be text fields, number1and number2. When the appropriate button is clicked, the function SendData1 or SendData2 is called. What you should notice is that all of the identifiers are appended with a number to indicate whether the button represents the first task or the second task (or more appropriately called the first or second transaction identifier). When the results are generated using the transaction identifier, we know which span element, result1 or result2, the result structures are destined for. Let s say that the text field with the identifier number1 contains 20, and the button associated with the function SendData1 is clicked. The generated structure that is sent to the server is represented using the following XML: 1 20
Looking for affordable and reliable webhost to host and run your business application? Then look no more and go to servlet web hosting services.

This entry was posted on Thursday, November 29th, 2007 at 10:17 am and is filed under Coldfusion. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.