Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Nov 24 21:12:36 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.4 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 mAP5CaDN006929 for ; Mon, 24 Nov 2008 21:12:36 -0800 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id mAP5B8XX000468 for ; Mon, 24 Nov 2008 21:11:08 -0800 Message-Id: <200811250511.mAP5B8XX000468@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Project 2 Date: Mon, 24 Nov 2008 21:11:08 -0800 From: Bill Cheng Someone wrote: > I just tried sending some larget files and ran into trouble... I'm not sure what "ran into trouble" mean. I hope FBI didn't show up at your house. :-) > do you have to > use select or some other function to determine when the socket cand SEND > more data? There should be no need. You should just call send() or write(). If the buffer is full, your call will be blocked. You need to make sure that it's okay to block your writing thread. -- Bill Cheng // bill.cheng@usc.edu