Felix Karpfen <[EMAIL PROTECTED]> writes:
> While this is not a WWWOFFLE problem, I am turning to the list for
> advice, since <Linux | WWWOFFLE> are outside the scope of the one to
> whom this query should be addressed.
>
> I recently participated in an online auction (of green coffee-beans) in
> which there were many other bidders eager to lodge their bids at (more
> or less) the same time (and the rules are - first in, best dressed). My
> existing setup coped adequately until I sent the message to purchase my
> selected quantities of the offered varieties. Then, because of delays
> caused by system load at the remote host, I got a time-out message
> from WWWOFFLE instead of the expected acknowledgement of the purchase.
> Consequently I was left totally in the dark about the <arrival |
> non-arrival> of my purchase request.
>
> Looking at the contents of the WWWOFFLE cache subsequently (when
> offline), it turned out that the remote host did receive the request and
> send an acknowledgement; the reply made it to the cache, but not to the
> screen of my computer.
>
> So the question is - which of WWWOFFLE's three timeout default-settings
> should be changed to avoid a repeat of this hiccough?
The three timeout options that WWWOFFLE has are the following:
socket-timeout = (time)
The time in seconds that WWWOFFLE will wait for data on a socket
connection before giving up (default=120).
dns-timeout = (time)
The time in seconds that WWWOFFLE will wait for a DNS (Domain Name
Service) lookup before giving up (default=60).
connect-timeout = (time)
The time in seconds that WWWOFFLE will wait for the socket connection
to be made before giving up (default=30).
The first one is the amount of time that WWWOFFLE will wait for data
on the connection from the server before it gives up. Each time that
some data is seen the timeout is reset and starts counting again.
The second one is the amount of time that WWWOFFLE will spend in
trying to get the IP address of the server from the system configured
DNS server.
The third timeout is the amount of time that WWWOFFLE will wait after
trying to open the connection to the server for the first data to
arrive. If no data arrives in the given time then WWWOFFLE will give
up.
In your case I think that the first one is the problem. You made the
connection to the server (since you found the message in the cache) so
it was not the other two timeouts that caused the problem since they
both relate to the start of the connection.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.9/user.html
