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?

Felix Karpfen

-- 
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)

Reply via email to