thrulay-users - select() and blocking sockets?
Subject: Discussion list for thrulay, a network testing tool
List archive
- From: Daniel Schaffrath <>
- To:
- Subject: select() and blocking sockets?
- Date: Fri, 27 Apr 2007 13:53:05 +0200
I don't understand how the select() approach matches the blocking read and write calls in the *_exactly functions. For a single stream client and the fork()ing daemon this is Ok. But in case of a client with multiple streams a blocking read on one socket might cause another socket to queue up. Or what am I missing here?
- select() and blocking sockets?, Daniel Schaffrath, 04/27/2007
- Re: [thrulay] select() and blocking sockets?, Federico Montesino Pouzols, 04/28/2007
- Re: [thrulay] select() and blocking sockets?, Daniel Schaffrath, 04/30/2007
- Re: [thrulay] select() and blocking sockets?, Federico Montesino Pouzols, 04/30/2007
- Re: [thrulay] select() and blocking sockets?, Daniel Schaffrath, 04/30/2007
- Re: [thrulay] select() and blocking sockets?, Federico Montesino Pouzols, 04/28/2007
Archive powered by MHonArc 2.6.16.