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

Ok, thanks Marcos. 

So if nobody objects I will execute according to this plan.

BR
  Claes

> -----Original Message-----
> From: Marcos Caceres [mailto:w3c@marcosc.com]
> Sent: den 9 januari 2014 05:42
> To: Nilsson, Claes1
> Cc: public-sysapps@w3.org; Kostiainen, Anssi; Isberg, Anders
> Subject: Re: [W3C SysApps Raw Socket API]: Status and proposed way
> forward
> 
> 
> 
> 
> On Friday, December 20, 2013 at 8:43 PM, Nilsson, Claes1 wrote:
> 
> > 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?
> 
> Sounds like a plan to me :)
>

Received on Thursday, 9 January 2014 12:53:17 UTC