RELATED SEARCHES
Sponsored Client-side Results:
Client-Side Templates
By:
Published: November 1, 2006
Internet navigation is done via either static or dynamic Web pages.
Static documents are coded in HTML and typically are used for sites that do not regularly update content. However, these simple documents do not allow much interaction with Web browsers.
Dynamic Web pages, on the other hand, are great for sites needing be updated on a regular basis.
Dynamic Web pages allow site interactivity. They may be generated in one of two ways. One option is through server-side scripting, which involves sending document requests through the server. These requests are interpreted using a scripting language. The dynamically generated document is sent as an HTML code.
The second model is the client-side model, which retrieves the page as is before displaying the document on the browser.
The Client-Side Model and Dynamic Web Pages
When a dynamic HTML document is requested, it is either generated on the client-side or the server-side. When a user requests a client-sided document, HTML code and a file containing a set of instructions (some of which also contain HTML code) are sent to the browser, which then generates a pure HTML document and displays it on the browser. Although the content is purely HTML, it is dynamically processed as per request of the user.
The following is a step-by-step process of the client-side model, as provided by vbip.com.
1. A Web author writes a set of instructions for creating HTML and saves it within an .htm file. The author also writes a set of instructions in a different language. This might be contained in the .htm file or in a separate file.
2. Sometime later, a user types a page request into their browser and the request is passed from the browser to the Web server,
3. The server locates the .htm page and may also have to locate a second file containing the instructions.
4. The Web server sends both newly created HTML stream and instructions back across the network to the browser.
5. A module within the browser processes the instructions and returns it as HTML within the .htm page.
6. The HTML is then processed by the browser, which then displays the page.
Advantages and Disadvantages of the Client-Side Model
One of the advantages of the client-side model is its increased access to the information and functions on the user's computer. Client-side scripting is popular among Web authors lacking access to their system's server since there is no additional software required. However, its disadvantages grossly outweigh its benefits, leaving the client-side model without much favor among Web authors and browsers alike.
Not all browsers are can understand, and therefore support, the client-sided model's scripting language. Unlike the server-side model, which can be supported regardless of system details, the client-side must be written in only certain types of scripting language. Furthermore, the scripting language may be inconsistently displayed among different browsers.
Client-Side Technology
ActiveX Control: This module provides such client-side functions as bar charts, times and database access, and is normally written in a language like C++ or Visual Basic. It is added to an HTML page via tags. However, since these controls were developed by Microsoft, they are only supported on Internet Explorer. In order to support this scripting technology, an ActiveX plug-in is needed. This greatly reduces cross-platform support and fewer Web authors use it to create dynamic templates and documents.
Curl: Client-side models normally download two separate files: one containing the .htm page and a second containing the instructions. With the utilization of a Curl plug-in, the second file is not downloaded at all. Instead, Curl replaces the HTML source and the file requested, speeding the download times and eliminating the use of scripting language. It only works on recent browser versions, though, and a plug-in is required.
Java: This is used in the form of applet codes and utilizes such functions as graphics and file handling. Java applets are supported on different browsers, most notably Microsoft and Netscape, which have built-in support through the Java Virtual Machine (JVM). When the browser downloads a Java file, it is done through the JVM.
JavaScript: This is the most widely used language for client-side scripting, especially since it is supported across many platforms and since it is an original browser scripting language, according to vbip.com. It is distantly related to Java, since both are based on C (see above).
VBScript: Last, but not least, is Microsoft's own scripting language, which competitively speaking is similar to JavaScript. It is not as fussy in terms of coding as JavaScript and it is preferred amongst Visual Basic developers since it is based on Microsoft's Visual Basic Program. However, if the Web user's computer does not contain a Microsoft browser, it will not support VBScript.
Sources:
Client-Side Scripting. 1 February 2006. Wikipedia. 31 October 2006. http://en.wikipedia.org/wiki/client-side_scripting /
Dynamic Web Page. 22 October 2006. Wikipedia. 31 October 2006. http://en.wikipedia.org/wiki/_dynamic_web_page/
Getting Started with ASP.net. Oleg Gdalevich. 31 October 2006. http://vbip.com/books/
Lohan, Scott. Language Choices for Client-Side Scripting. 30 November 2001. Pearson Education, Inc. 31 October 2006. http://www.peachpit.com/articles/article.asp?p=242 66&rl=1/
Static documents are coded in HTML and typically are used for sites that do not regularly update content. However, these simple documents do not allow much interaction with Web browsers.
Dynamic Web pages, on the other hand, are great for sites needing be updated on a regular basis.
Related Articles
The second model is the client-side model, which retrieves the page as is before displaying the document on the browser.
The Client-Side Model and Dynamic Web Pages
When a dynamic HTML document is requested, it is either generated on the client-side or the server-side. When a user requests a client-sided document, HTML code and a file containing a set of instructions (some of which also contain HTML code) are sent to the browser, which then generates a pure HTML document and displays it on the browser. Although the content is purely HTML, it is dynamically processed as per request of the user.
The following is a step-by-step process of the client-side model, as provided by vbip.com.
1. A Web author writes a set of instructions for creating HTML and saves it within an .htm file. The author also writes a set of instructions in a different language. This might be contained in the .htm file or in a separate file.
2. Sometime later, a user types a page request into their browser and the request is passed from the browser to the Web server,
3. The server locates the .htm page and may also have to locate a second file containing the instructions.
4. The Web server sends both newly created HTML stream and instructions back across the network to the browser.
5. A module within the browser processes the instructions and returns it as HTML within the .htm page.
6. The HTML is then processed by the browser, which then displays the page.
Advantages and Disadvantages of the Client-Side Model
One of the advantages of the client-side model is its increased access to the information and functions on the user's computer. Client-side scripting is popular among Web authors lacking access to their system's server since there is no additional software required. However, its disadvantages grossly outweigh its benefits, leaving the client-side model without much favor among Web authors and browsers alike.
Not all browsers are can understand, and therefore support, the client-sided model's scripting language. Unlike the server-side model, which can be supported regardless of system details, the client-side must be written in only certain types of scripting language. Furthermore, the scripting language may be inconsistently displayed among different browsers.
Client-Side Technology
ActiveX Control: This module provides such client-side functions as bar charts, times and database access, and is normally written in a language like C++ or Visual Basic. It is added to an HTML page via tags. However, since these controls were developed by Microsoft, they are only supported on Internet Explorer. In order to support this scripting technology, an ActiveX plug-in is needed. This greatly reduces cross-platform support and fewer Web authors use it to create dynamic templates and documents.
Curl: Client-side models normally download two separate files: one containing the .htm page and a second containing the instructions. With the utilization of a Curl plug-in, the second file is not downloaded at all. Instead, Curl replaces the HTML source and the file requested, speeding the download times and eliminating the use of scripting language. It only works on recent browser versions, though, and a plug-in is required.
Java: This is used in the form of applet codes and utilizes such functions as graphics and file handling. Java applets are supported on different browsers, most notably Microsoft and Netscape, which have built-in support through the Java Virtual Machine (JVM). When the browser downloads a Java file, it is done through the JVM.
JavaScript: This is the most widely used language for client-side scripting, especially since it is supported across many platforms and since it is an original browser scripting language, according to vbip.com. It is distantly related to Java, since both are based on C (see above).
VBScript: Last, but not least, is Microsoft's own scripting language, which competitively speaking is similar to JavaScript. It is not as fussy in terms of coding as JavaScript and it is preferred amongst Visual Basic developers since it is based on Microsoft's Visual Basic Program. However, if the Web user's computer does not contain a Microsoft browser, it will not support VBScript.
Sources:
Client-Side Scripting. 1 February 2006. Wikipedia. 31 October 2006. http://en.wikipedia.org/wiki/client-side_scripting /
Dynamic Web Page. 22 October 2006. Wikipedia. 31 October 2006. http://en.wikipedia.org/wiki/_dynamic_web_page/
Getting Started with ASP.net. Oleg Gdalevich. 31 October 2006. http://vbip.com/books/
Lohan, Scott. Language Choices for Client-Side Scripting. 30 November 2001. Pearson Education, Inc. 31 October 2006. http://www.peachpit.com/articles/article.asp?p=242 66&rl=1/
Featured Client-side Products:
