Hi again.
As I could not find a solution to the problem mentioned in my mail from
2013-08-19,
I am still trying to find a work-around.
I am almost done, but ...
I am now calling a local HOP service from a hand-written JavaScript program.
I use the xmlHttp from JavaScript like this:
this.xmlHttp.open("GET", url, true);
this.xmlHttp.onreadystatechange = this.getResults;
this.xmlHttp.send();
My HOP service replies for the given url with a:
(instantiate::http-response-xml
(backend (hop-get-xml-backend 'html))
(xml (<UL> ...)))
But the JavaScript side always reaches only state 2 instead of 4
(see http://www.w3schools.com/ajax/ajax_xmlhttprequest_onreadystatechange.asp
for an explanation of states).
What am I missing?
If I test my HOP service using
wget -S --header "Connection: Keep-Alive" <URL>
I see the following headers sent back by Hop:
HTTP/1.1 200 Ok
Connection: close
Content-type: text/html
Server: Hop
Length: unspecified [text/html]
I am wondering whether I should convince HOP
to use Keep-Alive. I checked the HOP source code (2.4.2)
for "http-response ::http-response-procedure", but
could not find a solution.
(As I see for similar replies from Apache+PHP servers,
they always use Keep-Alive, but I don't know
if this is only for efficiency or
if this is needed to make AJAX happy.)
Maybe somebody has some answers (or a small working example) to share
with the community?
Greetings
Sven
