Originally posted by Bear Bibeault:
One type of application in which it could be used is the much-asked-about pattern of updating the options in a drop-down box depending upon the selection of another drop-down.
Another usage could be in a web app such as my BlackBox game implementation. Currently, I make pseudo-asychronous requests back to the server whenever a "play" is made by posting to an invisible iframe and using returned Javascript to manipulate the parent page.
BlackBox could be a good testbed for me to really kick the tires of XmlHttpRequest and see if really offers any advtanges over the child iframe mechanism. One obvious benefit would be in simplifying the client-side window hierarchy by eliminating the iframe and the requisite cross-window communications. What disadvantages it would bring to the table would remain to be seen.
[ April 15, 2005: Message edited by: Bear Bibeault ]
back to the stone age of having to issue a lot of out.write commands
XML would be the way to go
There seems to be about equal work both ways
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |