SysApps Raw Socket API

I have submitted a proposal for a raw socket API: http://sysapps.github.com/sysapps/proposals/raw-socket/Socket.HTML.

The proposal is based on the Chrome Socket API, http://developer.chrome.com/apps/socket.html.

Comments:


*        This use of a Socket object, for which a set of methods is defined, is different from the Chrome Socket API, which uses a "socket id" as input parameter in all methods. An alternative would be to define a Socket interface constructor so that a Socket object for example is created with mySocket = new Socket ('tcp');. WDYT?

*        Do we need both the disconnect() and destroy methods() ?

*        So far support for server sockets through the methods listen() and accept() has been omitted. Not sure on use cases for server sockets.

*        I defined "CreateOptions" to support multicast use cases (UPnP SSDP etc) but I am not sure what is needed here. WDYT?

Sorry for missing the Jan 1 deadline.

Best regards
  Claes

[cid:image001.gif@01CDEE55.769F13A0]

Claes Nilsson M.Sc.E.E
Master Engineer, Research
Technology Research - Advanced Application Lab

Sony Mobile Communications
 Phone:  +46 10 80 15178
Mobile: +46 705 56 68 78
Switchboard: +46 10 80 00000
E-Mail: mailto:claes1.nilsson@sonymobile.com<mailto:claes1.nilsson@sonyericsson.com>
Visiting Address; Nya Vattentornet
SE-221 88 LUND,
Sweden
Disclaimer:
The information in this e-mail is confidential and may be legally privileged. It is intended solely for the named recipient(s) and access to this e-mail by anyone else is unauthorized. The views are those of the sender and not necessarily the views of Sony Ericsson and Sony Ericsson accepts no responsibility or liability whatsoever or howsoever arising in connection with this e-mail.Any attachment(s) to this message has been checked for viruses, but please rely on your own virus checker and procedures. If you contact us by e-mail, we will store your name and address to facilitate communications. If you are not the intended recipient, please inform the sender by replying this transmission and delete the e-mail and any copies of it without disclosing it.

Received on Wednesday, 9 January 2013 09:41:02 UTC