changeset 71891:54ec937ab5e4

(BUGS): High cpu load on windows server sockets fixed.
author Kim F. Storm <storm@cua.dk>
date Fri, 14 Jul 2006 09:32:14 +0000
parents b0584c551b8c
children 248ccc534803
files admin/FOR-RELEASE
diffstat 1 files changed, 0 insertions(+), 15 deletions(-) [+]
line wrap: on
line diff
--- a/admin/FOR-RELEASE	Fri Jul 14 09:32:02 2006 +0000
+++ b/admin/FOR-RELEASE	Fri Jul 14 09:32:14 2006 +0000
@@ -41,21 +41,6 @@
 	 '(hscroll-step 1)
 	)
 
-** TCP server processes do not work on Windows.
-
-TCP/IP server processes created with `make-network-process' consume
-excesive CPU on some Windows environments.  Usages of 50% and 100%
-CPU time have been observed on different Window XP configurations.
-Seems to be a problem in sys_select in w32proc.c.
-
-In its current form, it sys_select says the socket is ready, so we
-call server_accept_connection which again calls accept() which returns
--1 with errno == WSAEWOULDBLOCK (10035) indicating that there is no
-pending connection to accept.
-
-It seems that to fix this, w32 server sockets must use WSAAsyncSelect
-+ FD_ACCEPT to request notifications of incoming connections...
-
 
 * DOCUMENTATION