Techniques for the asynchronous loading of content on an existing Web page without requiring a full reload date back as far as the src attribute that could take any external URL, and by loading a page containing JavaScript that manipulated the parent page, Ajax-like effects could be attained. This set of client-side technologies was usually grouped together under the generic term of DHTML. Macromedia's Flash could also, from version 4, load XML and CSV files from a remote server without requiring a browser to be refreshed.
Microsoft's Remote Scripting (MSRS), introduced in 1998, acted as a more elegant replacement for these techniques, with data being pulled in by a Java applet with which the client side could communicate using JavaScript. This technique worked on both Internet Explorer version 4 and Netscape Navigator version 4 onwards. Microsoft then created the XMLHttpRequest object in Internet Explorer version 5 and first took advantage of these techniques using XMLHttpRequest in Outlook Web Access supplied with the Microsoft Exchange Server 2000 release.
The Web development community, first collaborating for remote scripting to enable consistent results across different browsers, created in 2002 a user-community modification to Microsoft Remote Scripting which was created to replace the Java applet with XMLHttpRequest.
Remote Scripting Frameworks such as ARSCIF surfaced in 2003 not long before Microsoft introduced Callbacks in ASP.NET.
In addition, the World Wide Web (W3C) Consortium has several recommendations that also allow for dynamic communication between a server and user agent, though few of them are well supported. These would include:
1. The object element defined in HTML 4 for embedding arbitrary content types into documents (replaces inline frames under XHTML 1.1).
Microsoft's Remote Scripting (MSRS), introduced in 1998, acted as a more elegant replacement for these techniques, with data being pulled in by a Java applet with which the client side could communicate using JavaScript. This technique worked on both Internet Explorer version 4 and Netscape Navigator version 4 onwards. Microsoft then created the XMLHttpRequest object in Internet Explorer version 5 and first took advantage of these techniques using XMLHttpRequest in Outlook Web Access supplied with the Microsoft Exchange Server 2000 release.
The Web development community, first collaborating for remote scripting to enable consistent results across different browsers, created in 2002 a user-community modification to Microsoft Remote Scripting which was created to replace the Java applet with XMLHttpRequest.
Remote Scripting Frameworks such as ARSCIF surfaced in 2003 not long before Microsoft introduced Callbacks in ASP.NET.
In addition, the World Wide Web (W3C) Consortium has several recommendations that also allow for dynamic communication between a server and user agent, though few of them are well supported. These would include:
1. The object element defined in HTML 4 for embedding arbitrary content types into documents (replaces inline frames under XHTML 1.1).
2. The Document Object Model (DOM) Level 3 Load and Save Specification
No comments:
Post a Comment