Hi,
I'm testing the latest htdig-3.2.0b4 snapshot (20020428).
I think that there is a problem with the htdig behavior and the
server_wait_time.
In Retreiver.cc:
---- cut here ----
// No HTTP connections available, so we change server and pause
if (max_connection_requests == 1)
server->delay(); // This will pause if needed
// and reset the time
---- cut here ----
You can see that htdig waits for server_wait_time only if
max_connection_requests equal to 1.
if max_connection_requests have a different value, htdig will never wait
server_wait_time timeout before to open a new HTTP connection to the
same web server.
Since htdig HTTP client supports the Persistent Connection mechanism, I
think the delay() function have to be called jut before this loop :
---- Retreiver.cc ----
// I think delay function have to be here
server->delay();
while ( ( (max_connection_requests ==-1) ||
(count < max_connection_requests) ) &&
(ref = server->pop()) && noSignal)
{
// stuff
...
}
---- Retreiver.cc ----
May be, I'm wrong and server_wait_time directive doesn't work with
persistent connection mechanism ...
Alain FORCIOLI http://www.VigiNews.com/
http://www.risc.fr/ [EMAIL PROTECTED]
http://www.april.org/ [EMAIL PROTECTED]
GPG Public Key: http://www.risc.fr/~af/gpg.txt
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
