Since I'd like to see this thread end soon, I propose that we vote on the following:
1. Leave the timeout at 60 seconds; There is no way to please everyone with a single value, as this is a *deployment* concern, so let's just leave it at 60 and move onto the real problem, which is:
2. Make the timeout configurable per-transport, as a deployment concern, without requiring that people write code. It should be possible for clients that talk to multiple web services providers to have different timeouts for those providers based on the different SLAs.
Eric
I'm not voting. I am going to observe that I like the idea of enhancing the read timeout error message, to say 'to adjust the value of this property, see 'some url', rather than just readtimeout.
