|
|
Posted by d on 01/12/06 12:23
"Chung Leong" <chernyshevsky@hotmail.com> wrote in message
news:1137004374.784280.165200@f14g2000cwb.googlegroups.com...
>
> C. wrote:
>> There are existing RPC implementations that do this a lot more neatly.
>> Ajax seems to be the prefered method these days - but its limited in
>> backward compatability (while iframe based versions are limited in
>> forward compatability).
>>
>> C.
>
> I don't think future browsers are going to abanden iframe. One problem
> with iframe implementation is that it can screw up the back-button
> behavior. And since the browser see the submission as a navigation
> event, it generates an audio alert, which can get very annoying.
That's not always a problem - that means you can use the back/forward
commands of the browser to move backwards/forwards through the dynamic
functionality of the site. Google uses that so you can go back/forward on,
say, google maps, and you don't leave the page, but you traverse your
browsing history within the actual map. If that makes any sense :)
Iframe and the XML requests are for completely different things. Getting
large amounts of data on a user signal? Use Iframe. Getting/setting some
variables on the fly? XML request. They're both suited to different tasks,
they just both happen to be good at getting data from a remote server.
> Another non-AJAX method is to dynamically create a script tag. It's
> somewhat limiting since the parameter has to be passed in the URL.
Which offers you nothing using the <iframe> method doesn't ;)
Navigation:
[Reply to this message]
|