Return-Path: william@bourbon.usc.edu
Delivery-Date: Tue Sep  9 22:47:29 2008
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m8A5lSOE016374
	for <cs551@merlot.usc.edu>; Tue, 9 Sep 2008 22:47:29 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m8A5kqJl007862
	for <cs551@merlot>; Tue, 9 Sep 2008 22:46:52 -0700
Message-Id: <200809100546.m8A5kqJl007862@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: select()
Date: Tue, 09 Sep 2008 22:46:52 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > We would only need a select on the listening socket right? Once we spawn a
  > process or thread with a new socket, it can be blocking right?

Please see my message with timestamp "Sun 07 Sep 09:02".
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>