The HTTP server supports HTTP 1.1, so I suppose it should use a
perisistent connection. I checked if the webserver was configured
properly, and it is.
I did some research on the subject and looked at the wireshark output
of a Mozilla firefox 3.0 quick search bar search (which also uses
XmlHttpRequest). The requests in this log are done via a single TCP
connection. I compared the source js to my own js but there where no
functional differences.
Also checked websites as http://ajaxref.com/ http://ajaxpatterns.org/
and http://radio.javaranch.com/pascarello/2006/03/30/1143735438047.html
but could not find any info.
Anyone got a clue?
Wilco
if is not your code, maybe is your data... your URL parameter, like
http://www.mysite.com/foo/bar/caa/zeta
vs
?data=newdata&json=()
maybe the god's of software are mad at you for use the wrong type.
--
--
ℱin del ℳensaje.
What I did in the past is opend a connection, wait for a response then close
the connection(delete the object).
This is much different than when it is run under IE. Firefox doesnt like to
make multiple requests.
My application was a remote appliance that used ajax to get display data. It
was a PIC running Mchips stack.
I used the default socket count.
Hope that helps.
Martin