- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 13 May 2013 10:36:30 -0700
- To: "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
- Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>, "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>, Isaksson, Björn <Bjorn.Isaksson@sonymobile.com>
On Mon, May 13, 2013 at 3:57 AM, Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com> wrote: > 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. Well, if the implementation doesn't support TCP server sockets they shouldn't expose the TCPServerSocket constructor at all. This is probably worth pointing out in the spec. At that point it's clear that attempting to create one will yield an exception in Javascript. > 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? I assume that setting up a server requires several long-running steps, i.e. steps that require IO. Such steps should not be taken synchronously from the TCPServerSocket constructor since that will result in jank in the UI of the application. / Jonas > 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 17:37:27 UTC