W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 2001

Re: Client Side API - HTTP Connections

From: John Philip Anderson <jpanderson_215@hotmail.com>
Date: Wed, 07 Mar 2001 19:12:46 -0000
To: ylafon@w3.org
Cc: www-jigsaw@w3.org
Message-ID: <F128TR60oVexDAeys8F00001fd6@hotmail.com>
Dear Mr. Lafon,

Thank you very much for responding to my request for help.  Below is my 
"debug mode" output from HttpManager and HttpBasicServer.  I used 
setPipeline(false) on each Request (so I assume that this is not a 
pipelining problem per se).  Yet, I believe that you are right in supposing 
that the server did not reply entirely (this is where the "debug mode" 
output ends and when my software snags for a period of about a minute).  So, 
I believe that I need some way to set a timeout for the server to respond my 
request.

As previously noted, the HttpManager.setRequestTimeout() method has not been 
implemented and the HttpManager.setTimeout() method does not appear to 
affect this intermittent transaction delay problem.  So, I am working on a 
solution.

Do you know if a Request created by HttpManager has a "RequestObserver" or 
not?

	Truly yours,
	John Philip Anderson
	jpanderson215@hotmail.com

~~~~~~~~~~~~~~~~~~~~~~~~~
"debug mode" output from HttpManager and HttpBasicServer

Running request: http://foo.bar.com
+++ notify conn_count 1 / 5
+++ connection used
foo.bar.com/216.39.109.40:80[0]: runs[unknown] http://foo.bar.com
*** foo.bar.com:80 major=1, minor=0, ka=false
+++ delete conn_count: 0
Request done !
Running request: http://foo.bar.com
+++ notify conn_count 1 / 5
+++ connection used
foo.bar.com/209.185.172.89:80[1]: runs[10] http://foo.bar.com
+++ delete conn_count: 0
Request done !
Running request: http://foo.bar.com
+++ notify conn_count 1 / 5


>From: Yves Lafon <ylafon@w3.org>
>To: John Philip Anderson <jpanderson_215@hotmail.com>
>CC: <www-jigsaw@w3.org>
>Subject: Re: Client Side API - HTTP Connections
>Date: Wed, 7 Mar 2001 18:24:52 +0100 (MET)
>
>On Tue, 6 Mar 2001, John Philip Anderson wrote:
> >
> > 1.) I have ran into a problem that appears to be similar to that 
>previously
> > described by Mr. Katha et al. in a message thread titled "Re: Client 
>Side
> > API - HTTP Connections" which was posted from January 31 to February 5,
> > 2001.  Specifically, I also have been "experiencing intermittent delays 
>in
> > the time required to complete requests" during multiple requests to the 
>same
> > host.
> >
> > However, I have apparently solved my problem by lowering the request 
>timeout
> > threshold to 1000 milliseconds (from whatever the default value is) by
> > adding one line of code to my software:
> >
> > 	manager.setRequestTimeout(1000);
> >
>
>I didn't have time to investigate on this, but did you try to recompile
>the classes in debug mode to see if it is because the server didn't reply
>entirely while pipelining was used? related to the opening of too many
>connections, hence waiting for one of them to finish?
>Thanks,
>
>--
>Yves Lafon - W3C
>"Baroula que barouleras, au tiéu toujou t'entourneras."
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Received on Wednesday, 7 March 2001 14:13:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:35 GMT