The Internet Is Facing Profound Balkanization
In these days millions of people are using America online (AOL) or web TV to browse the internet and these implement only a subset of the full features of either browser. Several different versions of each of the browser are currently in use and the browsers are frequently not completely backward compatible.
The support for scripting languages is inconsistent and advanced script features frequently generate errors in older browsers. Increasingly people are using Pads, cellular phones and other hand-held devices to interact with the web. These devices often don’t have the processing power to handle complex scripting and fervently support fairly basic HTML only. And adding another browser only exacerbates rather then helps the problem. One consequence of this is that while the latest browsers have features such as the ability to display formatted XML on the client in this fashion because the vast majority of all browsers out these do not support XML.
Therefore developers have been moving to sever side scripting solutions for a while. Technologies such as active server pages Java server pages and Cold Fusion let developers write script pages that process information or data on the sever and then format the result in an HTML format that can be sent to the client. Any of these can determine what type of client they are writing to then adjust their output accordingly. There is problem with this approach. Concentrating on active server pages the traditional architecture of a sever page lets developers often resulting in a difficult to follow and computational mess especially when client side scripting exists as well. While it is possible to flow what is going on in this combination of bracketed Tags with in tags, multiple intermixed script Languages and the lack of any programmatic flow makes such an ASP difficult to use and completely impossible to migrate to different systems. The irony here is that the preceding code is typical of how ASP pages are written on the Web, although the language itself is capable of producing far cleaner results without getting into details about what is inside the XML or XSL files, the same script could effectively be reproduced using ASP in conjunction with XML, as demonstrated. This sample includes two object Multiples. One is Browsers, which gets browser capabilities information. And other is XSL Util Parameter, which sets parametric information within the XSL documents. Notice here that the actual names of the files to be retrieved are passed as query script for any page that has both an internet Explorer and a Netscape XSL filter.
While the code is perhaps a little denser in the preceding example, it is only because there is not much actual output text in the first ASP page. XML can significantly reduce the overhead of ASP files and speed up their exaction because the bulk of the actual processing takes place within optimized DLLs rather than in slower interpreted code moreover it become easier to separate the data preparation layers from the presentation layer; the preceding script could be rewritten to take an XML object as a parameter and you could then subside the XML object as a database query or passed as an object from a post command rather then load an explicit XML file from the server.
For more information visit to- Website Designing Service And Website Designer
Processing your request, Please wait....
