Undolog.com

Like many Web developers know, before the advent of the XMLHttpRequest object, the problem of the reloading of a Web page was solved with the technique of hidden FRAME or IFRAME. This simple trick has allowed many people to solve some problems otherwise unsolvable interface. An advantage of using the hidden frame, among other things, was the ability to maintain the browser's HISTORY! Which does not allow the XMLHttpRequest object.

In addition to techniques which use HTML FRAME or IFRAME hidden, it is possible to use Flash as a sub-channel of communication between the page and the Server. Some experience in this direction are still in development (see for example Fjax ). The idea is to "hide" a Flash movie within the HTML page (as happened with FRAME) and communicate with it via JavaScript (or VBScript for Microsoft environment only).

However, this technique a number of hidden pitfalls. First of all forces the end user to install the Flash plugin, and then a solution is not HTML (pure) clean. It also requires, however, prompted the use of Javascript and Flash as an interface between the page, so much it's worth using the XMLHttpRequest object. Then when you start to write a framework in ActionScript want to do everything in Flash. Here is that the variation to the XMLHttpRequest object begins to have little sense.
Ultimately if you do not want to use the XMLHttpRequest object, we must rely on the now-established technique of hidden frame. There are even those who use just a mixed technique: XMLHttpRequest + IFRAME!

However, now, Ajax (in the form of the XMLHttpRequest object) has proved so successful that in the future will be the XMLHttpRequest object that is supported by improved browser vendors (Microsoft, Mozilla, Opera, etc ...). In practice, XMLHttpRequest will be a default component (as is already in FireFox) within the browser, accessible via Javascript! So why not use it?

This article was useful to you?:

Loading ...

• 

• Tweet