Should be either the same as for FF or not supported at all.

I use code that looks like this in JS to asynchronously get data from the server with xmlhttprequest:

Note that some of that code is a little specific for my project. I'm talking about that check that makes sure no other request can be made until data was received from the previous request. In your project you will probably want to change this...

See, now those are good tutorials. They just give you the facts, plain and simple. I really hate it when they pad the tutorial with a bunch useless crap to "ease" the learning process. It just makes it so you have to sift through it all to really get anything done... the whole world should think exactly like I do!>:(

[edit]
Although I must agree with the second tutorial that the first tutorial may not have had the best code examples.

http://www.maxkiesler.com/index.php/weblog/comments/50_ajax_reference_websites_from_around_the_world/ D:

You cannot add a node from one document into another. You need to import it (importNode ?), but of course IE6 doesn't support that.

The whole "AJAX" name is a joke. No one seriously uses XML with it. It's really "AJAJ" or "AJAH". Look for what's known as "JSON". It's basically a way to convert XML like data into a string that represents a JavaScript object.

AJAJ example:

server generates:
{options:[{value:0,text:"zero"},{value:1,text:"one"}]}

client evaluates it:
eval("var response = " + json);
alert(response.options[0].value);

Or alternatively use AJAH and just pass it as HTML, and use foo.innerHTML = HTML;.

I meant to comment on this:

Don't ever check the browser type to determine functionality. Always check browser features, starting with the standard ones first:

if (foo.addEventListner) {
  // W3C Model
}
else if (foo.attachEvent) {
  // IE Model
}

The only times you want to check the user agent string with JS is if a certain browser has a glitch that you need to work around. For example, I check for the literal string "Safari" on the dynamic combobox widget because Safari does not support CSS system colors, so I have to provide default colors.

That is the only future compatible method. If I were to check for features, I might get the detection wrong if another browser matches it or Safari changes functionality. (Obviously if they ever fix this problem, then I would need to add a version check as well.)

Of course it does. The server serves plain text. This text can be interpreted on client side as you wish, either as XML or JSON or anything else. On the server you just create a string containing JSON code, write it to the response object and that's it. I only know ASP, but I suppose it's similar in othe server side scripting languages. You just do something like

dim json as string
json = "{options:[{value:0,text:"zero"},{value:1,text:"one"}]}"
Response.Write(json)

and on the client in JS you do something like

var json = req.responseText;
eval("var response = " + json);

There are also many JSON classes available for scripting languages. The one I use for PHP works like:

$response = array(
  'foo' => 'bar'
);

$json = new JSON;
echo $json->encode($response);

It may seem like overkill at first, but it becomes quite nice when you have a very dynamic response to build. Plus, it automatically handles converting UTF-8 encoded strings to proper JS escapes (eg, "\u00A9").

You're doing something wrong, then. The examples above will not do that.

Perhaps include some code?

Marcello

Here's it (I still didn't converted it to JSON)

Client-side, when the selected item of a <select> changes, this deletes all the current <option>s in it and loads a js from listacomuni.php

Server-side, generates js that will add the new <option>s to the <select>

While the code isn't 100% fixed (I still have issues alternatively in IE and FF ), when the query returns few rows it generates the whole script, but if the rows are many the script gets broken (I saw this by replacing eval() with alert() in the client-side script

An example is attached (couldn't resist to try the new upload thing )

while(req.readystate != 4);
just like that?

All your open()'s have stray php. Is that intended?