| Subject: | DIfferentiate between socket connect timeout and Webserver response timeout |
Scenario: you wish to call one of several servers which will complete the TCP handshake in under a second, but then take a minute to return the data.
If one of the servers is down, you want to swiftly switch to a different server, without waiting the full minute for the response timeout.
Could libwww be updated to add in a new connect_timeout attribute which defaults to the current timeout ?