AJAX window.location .href.indexOf(" http")==-1)

[whisher]

Hi.
Sorry to disturb you but I can't
figure out its use in this snippet
(Found in many scripts about Ajax)
function loadpage(page_r equest, containerid)
{
if (page_request.r eadyState == 4 && (page_request.s tatus==200 ||
window.location .href.indexOf(" http")==-1))
{
document.getEle mentById(contai nerid).innerHTM L=page_request. responseText;
}
}
Can you enlighten me ?
Thanks in advance ;)
Bye.

[Randy Webb]

Jonas Raoni said the following on 11/20/2006 11:14 PM:

Randy Webb escreveu:

>kd****@gmail.co m said the following on 11/20/2006 8:49 PM:
[...]
And if you are running it locally the readyState will never be 200.

Also checking for the constant "200" isn't nice in my opinion,

Then what *should* you be checking for? 2* ?

because what defines the status is just the first digit of the code, the others
act as a kind of sub-status.

And in this case, you want 200 and 200 only.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[shimmyshack]

This script was part of a library, Jonas and I are making the point
that as AJAX matures the complexity of this part of the js that checks
for response codes should start reflect the full structure of the RFC
where 200 _isn't_ always what you want or what you get.

For instance, a 304 header check could be implemented here, if
somewhere else in the code caching is being used, so that you get a
benefit in using AJAX, if each time you click a button you get the same
200 with response body, this is hardly using AJAX to its full, however
if you have implemented some form of caching, then the headers sent
could be a bit more advanced and the codes back could save you time in
both receiving the data, parsing it and rendering it.

I would personally prefer it if libraries didnt just assume that 200 is
the only code out there that is useful to AJAX.