Ciao "talponi" miei,
I want to propose you the issue of at least another attribute regarding
htnet library, and in particular TCP connections (so valid for HTTP and,
other application layer protocols such as FTP - when implemented).
We already have the 'max_retries' attribute, which refers to the
application layer, and so far to the HTTP connection. It sets how many
times we should try to retrieve a document when we don't obtain a valid
result for the connection (server not found, port not found, no connection,
...). As Geoff said earlier, there's a deeper retry system that should be
issued and regards the TCP connection and its timeout management. As far as
the actual code is concerned, we retry only <once> and then we wait for 5
seconds.
As we already have an attribute for delay management ("server_wait_time"),
why don't we use this instead of 5 seconds? Or maybe we can issue a new
one, just for TCP connection retry and to be used after a timeout occurs in
order to let the sever wait <x> seconds before next attempt. And how many
attempts should we do? I propose to issue a new attribute called maybe
"tcp_max_retries" and able to manage TCP connections retries.
If we issue this one (or two) attribute (s) we will be able, with our new
configuration system, to set them however we want.
Let me know
-Gabriele
-------------------------------------------------
Gabriele Bartolini
Computer Programmer (are U sure?)
U.O. Rete Civica - Comune di Prato
Prato - Italia - Europa
e-mail: [EMAIL PROTECTED]
http://www.po-net.prato.it
-------------------------------------------------
Zinedine "Zizou" Zidane. Just for soccer lovers.
-------------------------------------------------
-------------------------------------------------
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
