© 2005 Goetz HellerTable of Contents Copyright Note back
The basic idea relies on a simple construct on the client side and is as follows:
In order to achieve such a communication the client application frame creates an HTML document with a form inside the HTML Data Port. The form contains a field to which data to be sent to the server is assigned as its value ("request"). The data would be base64-encoded and optionally may be encrypted before.
Another application could be such that the response data contains an HTML fragment which is used to replace the contents of the work area, or simply to change some data inside the work area be it visible or not. For instance, imagine a deeply neested hierarchy structure represented in a way a file system explorer would do. At the beginning, only the nodes on top of the hierarchy are expanded; the nodes below are collapsed. Hence there is no need to have all the hierarchy data inside the document at once. Instead, data is requested from the server only on demand - when a user wants to expand a node which has not been populated so far. Since in general only a fraction of all the nodes is visited by a user this saves a lot of network traffic.