- From: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
- Date: Mon, 13 May 2013 12:57:33 +0200
- To: 'Jonas Sicking' <jonas@sicking.cc>, "public-sysapps@w3.org" <public-sysapps@w3.org>
- CC: "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>, "Isaksson, Björn" <Bjorn.Isaksson@sonymobile.com>
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 10:58:02 UTC