On 7/14/03 04:53 PM Doug Davis <[EMAIL PROTECTED]> wrote: > As you indicated, the value you pick will never make everyone happy. The > best you can hope for is to make sure that there are sufficient APIs such > that people who use the DIIs, stubbies or whatever can get access to that > setting easily. Personally, I think Axis should default to "0" (no > timeout) because by default I would want the system to be as > lenient/tolerant as possible - and if someone is running in an environment > that requires stricter controls they can set it as such - picking any value > other than zero give preference to whatever machine/environment the axis > developer who wrote that line of code happens to be using at that moment.
I have been running into major problems with people using axis on the client claiming that our server is broken (prior to the 60 seconds change). What happened (as stated in #18277) was that they had a broken router which would not return the axis response to the client. In the end the server got the request, send the response, and the client was there sitting forever in a blocking call. Should a user be forced to use a debugger to see why an axis client is blocking (timeout=0)? I can't proof it right now, but as long as you see data on the wire the timeout should not create problems at all. Jens
