Timeout status codes are thoroughly messed up

2004-03-15 Thread rbb
I have spent the last half hour or so trying to make the socket timeout tests pass on Windows. I couldn't make it happen, so I finally started reading through the code. It turns out that we have a number of error codes that mean that a timeout has expired. On any platform that uses

Re: Timeout status codes are thoroughly messed up

2004-03-15 Thread Cliff Woolley
On Sun, 14 Mar 2004 [EMAIL PROTECTED] wrote: This needs to get resolved. I believe the fix is to simply add the correct checks to APR_STATUS_IS_TIMEUP, but I also would like to know if we really need to keep APR_STATUS_IS_ETIMEDOUT at all. Can we mark it deprecated? +1 as far as I'm