Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Aug 31 19:11:44 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 m812Bipa029553 for ; Sun, 31 Aug 2008 19:11:44 -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 m812JGuH004299 for ; Sun, 31 Aug 2008 19:19:16 -0700 Message-Id: <200809010219.m812JGuH004299@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Regarding Warm-up proj 1 Date: Sun, 31 Aug 2008 19:19:16 -0700 From: Bill Cheng Someone wrote: > I had some queries regarding project 1 : > 1) the specs says "You must not fragment the response message > into packets or multiple messages". > Does it mean I can send the entire response (i.e. header and data > part) all at once to client , or should it be sent  byte by byte. You must send it one byte at a time. But you should keep in mind that TCP has a stream abstraction. So, you should not even think about breaking a message into packets. > 2) For sending message byte by byte I am first taking values in > structure and then copying the values in character array buffer. > Then I am sending one byte at a time from client . At server read > one byte at a time in buffer and then store data in structure. I > just want to verify if I am using correct approach I'm sorry but I cannot answer your question in e-mail! Please see the first bullet in: http://merlot.usc.edu/cs551-f08/description.html#email If you really want to talk about this, please come to my office hour to discuss this. > 3) Can we use List or int array to store pids of the child > processes? Because the server needs to shutdown gracefully, the server should keep track of the child processes. You can use a list or a dynamic array to keep track of the child pids. I'm going to add some notes to the spec about this. -- Bill Cheng // bill.cheng@usc.edu