Date: Sun, 24 Mar 2002 13:46:40 +0100 (MET) From: Lars Christensen <larsch@cs.auc.dk> Subject: [webricken:80] Re: Help with a 408 error To: webricken@notwork.org Message-Id: <Pine.GSO.4.44.0203241341020.28805-200000@peta.cs.auc.dk> In-Reply-To: <20020323.013451.63216433.gotoyuzo@kotetsu.does.notwork.org> X-Mail-Count: 00080On Sat, 23 Mar 2002, GOTOU Yuuzou wrote: > > The next two seem to fix the above problem. It changes the server model a > > little. When a request has been processed, the thread returns the sockets > > to the main loop.. The main loop will IO#select on the sockets and return > > them to a thread when there is incoming data. > > This approach seems appropriate to use the threads efficiently. > However, it has to be considered about the processing which > performed only when connection is established. This problem is > appeared in webrick/https. Second try. This time I select on @listeners and sockets in two seperate threads to avoid using @listeners.include?. Also, I removed the timeouts on the selects and used a pipe to notify the socket-listening thread when a socket is being returned to the main loop. -- Lars Christensen, larsch@cs.auc.dk80_2.txt (attatchment)(tag is disabled)