dank at eecs.berkeley.edu
Sun Sep 23 13:44:53 PDT 2007
Eric Cheung wrote:
> The spec says "If the client or server is unable to recover from the
> socket error, it should terminate."
> However, this is really vague and depends on which errors you think are
> "recoverable". Should the client or server terminate if it gets any
> socket error instead?
This is a judgment call that you'll have to make.
> - Eric
> Lisa Fowler wrote:
>> I hit reply before properly replying.
>> On 9/22/07, Lisa Fowler <fowler at eecs.berkeley.edu> wrote:
>>> On 9/22/07, Nescio Nomen <nescionomen at gmail.com> wrote:
>>>> Do we have to implement some kind of timeout anywhere in our code? I don't
>>>> think the specs mention it, and I see that Beej and most other people do not
>>>> implement a time out for example in select().
>> This is the part for you to decide.
>>>> Also, if we get some kind of error in our server code (eg an accept() fails
>>>> at some point or read() returns -1), we should *always* just print an error
>>>> and terminate with exit(1), and *not*, for example, try to recover and
>>>> continue listening for more clients. Should we ever attempt a recovery?
>> THIS part, we decide. And we decide that you should not attempt
>> recovery if it's an error like what you describe.
>> ee122 mailing list
>> ee122 at mailman.ICSI.Berkeley.EDU
> ee122 mailing list
> ee122 at mailman.ICSI.Berkeley.EDU
More information about the ee122