RE: Error handling for TCPServerSocket

In addition, for errors that occurs after the socket has successfully been set up we already have the error event but we need to add that the event is not only fired when a new connection attempt to the TCP server socket cannot be served, but also when an error in the underlying layer occurs, e.g. network connection is lost. 

Would this be sufficient?

Claes

> -----Original Message-----
> From: Nilsson, Claes1
> Sent: den 13 maj 2013 12:58
> To: 'Jonas Sicking'; public-sysapps@w3.org
> Cc: Edenbrandt, Anders; Isberg, Anders; Isaksson, Björn
> Subject: RE: Error handling for TCPServerSocket
> 
> Hi Jonas,
> 
> Yes, the error handling for TCPServerSocket might have to better
> defined.
> 
> In the description of the steps for the TCPServerSocket constructor I
> guess that we should add a statement saying that an exception is thrown
> if the server socket cannot be created, for example because the
> implementation does not support TCP server sockets.
> 
> However, I don't know if we need an event stating that the server has
> been successfully set up. Would a successful execution of the server
> socket constructor be enough?
> 
> Claes
> 
> > -----Original Message-----
> > From: Jonas Sicking [mailto:jonas@sicking.cc]
> > Sent: den 12 maj 2013 03:52
> > To: public-sysapps@w3.org
> > Subject: Error handling for TCPServerSocket
> >
> > The error handling for TCPServerSocket is somewhat unclear.
> >
> > What errors can be raised if we fail to open the server? What errors
> > can be fired once the server is successfully set up?
> >
> > And how does the caller know that the server has been successfully
> set
> > up?
> >
> > / Jonas

Received on Monday, 13 May 2013 11:07:31 UTC