Delivery-Date: Sun Sep  7 18:22:39 2008
Message-Id: <200809080121.m881LULw021391@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: CS 551
Date: Sun, 07 Sep 2008 18:21:30 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > If the server is sending the data, and if the client closes the
  > connection, how will the server know that the client connection has
  > closed because the server may have already sent all the data, by then?

If the server has finished sending the data, it should
just shutdown and close the socket.  Then it wouldn't
care if the client is closing the connection or not.
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>


On Sun, Sep 7, 2008 at 2:18 PM, Bill Cheng <william@bourbon.usc.edu> wrote:
> Someone wrote:
>
>  > If the server is in a long data transfer with the client during which the
>  > server process is interrupted and terminated, should the client display the
>  > data that it has received until that point or shoud it just say server
>  > terminated and quit,
>
> If the client does not receive the whole message, it should
> print an error message and quits.
>
>  > and what about vice versa, if the client shuts down
>  > what should happen?
>
> The child thread or process should just quietly terminate.
> If you use a logfile, you can log this error to the logfile.
> But you should *not* write the error to stdout or stderr.
> --
> Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>
>
>