W3C home > Mailing lists > Public > public-sysapps@w3.org > December 2013

[W3C SysApps Raw Socket API]: Status and proposed way forward

From: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
Date: Fri, 20 Dec 2013 11:43:02 +0100
To: "public-sysapps@w3.org" <public-sysapps@w3.org>, "'Kostiainen, Anssi'" <anssi.kostiainen@intel.com>
CC: "Isberg, Anders" <Anders.Isberg@sonymobile.com>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA3024867D18E85@seldmbx03.corpusers.net>
Hi all,

Unfortunately I have had to focus on other tasks than the Raw Socket API the last months and the specification, http://raw-sockets.sysapps.org/, has not been updated since October 1st. However, I will resume my activity with this specification in January after the season holidays.

The main task is a rewrite of the API to be based on the Streams API. Conclusions from SysApps meeting at TPAC Nov 12, 2013, were that the Streams work is complicated and will take time to stabilize. So it was proposed to handle current issues in the current version of the Socket API and publish a new working draft and after this create a new branch for a Socket API based on Streams but keep the current version as a parallell track (as we don't yet know the outcome of the work on Streams). However, Marcos raised the point that we should not give a confusing message by working with two parallel versions by making a new public working draft of the non-streamed based version. So I suggest that I instead create a subfolder and saves the current version (similar to what I have for the first Berkeley-style version) and don't do a re-publication. Then the continued work is based on Streams.

WDYT?

Anssi, in addition, do you have feedback from your implementation and proposals for changes that may go into the current specification before I save it in the subfolder?

Best regards
  Claes


Claes Nilsson M.Sc.E.E
Master Engineer - Web Research
Advanced Application Labs

Sony Mobile Communications
Tel: +46 705 56 68 78
sonymobile.com<http://sonymobile.com/>

[cid:image001.jpg@01CEFD71.68A86040]




image001.jpg
(image/jpeg attachment: image001.jpg)

Received on Friday, 20 December 2013 10:43:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:18 UTC