Advanced Requests and Responses in Ajax 209
An anonymous reader writes "The Web is no longer a place where simple applications are tolerated; 'users have become more advanced, customers expect robustness and advanced error reporting, and managers are fired because an application goes down 1 percent of the time. It's your job then, to go beyond a simple Ajax application that requires a more thorough understanding of XMLHttpRequest.' This DevWorks article tries to help developers use Ajax to build a solid foundation in which an application handles errors and problems smoothly."
Re:AJAX? (Score:3, Informative)
Too bad it requires JavaScript!
Re:AJAX? (Score:3, Informative)
Re:AJAX? (Score:2, Informative)
http://en.wikipedia.org/wiki/AJAX [wikipedia.org]
Pretty sparse (Score:4, Informative)
Any decent webdev entering the field should know about http status codes, HEAD requests and all that. Also it should be noted that article didn't even mention how many times state 3 is hit for a particular request - I got caught by that one once.
Re:Users.. (Score:2, Informative)
If high availability is key then you'd better not be using anything beyond HTML.
Uh... how about having an app degrade nicely? In most cases it's not that tough. So for the large majority that can take advantage of your whiz bang web app, go ahead and use AJAX (where it makes sense) and just be sure to have it degrade nicely for browsers that are not ajax aware and then also for browsers that are not handling javascript.
Corrected URL (Score:5, Informative)
http://download.boulder.ibm.com/ibmdl/pub/softwar
Taking the "%20" away from the final "/" made it work.
(There should be no spaces in the URL.)
Re:AJAX? (Score:4, Informative)
Anyway, thanks again.
Re:AJAX? (Score:3, Informative)
You'd be wrong. I don't believe slashdot uses any Javascript, except maybe some ad stuff. And even if it did, that's not a good definition. The point of Ajax is updating the client's display with new data from the server without reloading the entire page. This is why Ajax is so trendy - these pages are more pleasant to use because they respond more quickly, and without unrelated parts of the display going away and coming back or causing everything to scroll away from what you were looking at.
Ajax accomplishes this with the XMLHttpRequest() object. (It's a misnomer - XML doesn't have to be involved at all.) It's just a way to issue a request and execute some code when it completes (by success, failure, or timeout). That code can update a status bar, add some text to the page, or do something more sophisticated.
I would prefer the JSON way (Score:4, Informative)
Re:AJAX? (Score:2, Informative)
Re:No longer tolerating what?? (Score:1, Informative)
Click on the word "Sections" in the menu....
Re:AJAX Privacy and Security? (Score:3, Informative)
The browser history is not available for security reasons. Off the top of my head, I don't remember if anything more than the screen resolution can be obtained. Really, you're not getting back anything useful. Just a lot of statistics that the Javascript uses to do its job.
Until the introduction of the XMLHTTPRequest object, developers were limited in how they could bring this information into the server.
Hidden IFrames have all the power of XMLHTTPRequest. There is a "click" in Internet Explorer, but all other cues are missing.
Browsers like Firefox can limit the use of javascript to do popo-up ads, alter toolbars and such, but I see nothing regarding security control of the XMLHTTPRequest object.
Depends on the browser, but many browsers chose the path provided by Java Applets. i.e. An AJAX application can only ship back data to the server it was downloaded from. That means that the server needs to act as a proxy if it wants to send calls elsewhere on the Internet.
Re:I would prefer the JSON way (Score:3, Informative)