From 1670d7cdac5b300af85aadb56d211adf284e064d Mon Sep 17 00:00:00 2001
From: Glenn Maynard <gmaynard@users.sourceforge.net>
Date: Tue, 14 Feb 2006 03:39:35 +0000
Subject: [PATCH] fix data lost at the end of the connection

---
 .../src/archutils/Win32/CrashHandlerNetworking.cpp  | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/stepmania/src/archutils/Win32/CrashHandlerNetworking.cpp b/stepmania/src/archutils/Win32/CrashHandlerNetworking.cpp
index a0268bb968..757dd620db 100644
--- a/stepmania/src/archutils/Win32/CrashHandlerNetworking.cpp
+++ b/stepmania/src/archutils/Win32/CrashHandlerNetworking.cpp
@@ -226,13 +226,18 @@ int NetworkStream_Win32::WaitForCompletionOrCancellation( int iEvent )
 
 		m_Mutex.Unlock();
 
-		/* If the socket was closed while we were waiting, stop. */
-		if( (events.lNetworkEvents & (1<<FD_CLOSE_BIT)) )
-			return WSAECONNRESET;
-
 		/* If the event didn't actually occur, keep waiting. */
 		if( !(events.lNetworkEvents & (1<<iEvent)) )
+		{
+			/* If the socket was closed while we were waiting, stop.  Note that when the
+			 * connection closes immediately after sending data, we'll receive both this
+			 * message and FD_READ at the same time.  Only do this if the event we really
+			 * want hasn't happened yet. */
+			if( (events.lNetworkEvents & (1<<FD_CLOSE_BIT)) )
+				return WSAECONNRESET;
+
 			continue;
+		}
 
 		return events.iErrorCode[iEvent];
 	}