Hi,
On Windows serf doesn't see the difference between a failed connect and a lingering close. This causes serf to automatically reconnect. See http://subversion.tigris.org/issues/show_bug.cgi?id=3832 for a few more details. Reproduction: svn ls http://127.0.0.1:23456/svn On FreeBSD this gives a proper 'Connection Refused' error, but on Windows the application just gets in a loop. I found this issue because this sometimes causes the buildbot to get stuck when the httpd instance crashes on some assertion. Once I start using 1.7.0 for real use this problem will be much worse because there is no clean way to get out of this error. (Only killing the application works; which would include losing work for Subclipse and AnkhSVN users). Either Serf should detect the right error, or Apr should implement a real poll handler on Windows (available since Windows Vista) which should provide more error information. Bert
