W3C home > Mailing lists > Public > public-webcrypto@w3.org > February 2013

Re: PROPOSAL: Close ISSUE-24 - Defining a Synchronous API

From: Richard Barnes <rbarnes@bbn.com>
Date: Mon, 4 Feb 2013 15:02:48 -0500
Cc: public-webcrypto@w3.org
Message-Id: <CDBEB6DF-7ABA-4D63-9752-50C2E8F549A3@bbn.com>
To: Ryan Sleevi <sleevi@google.com>
No objection to closing this.

But on a related not, could you provide a link for the group to what you mean when you say a "Promises-style API"?  I've had trouble finding good information about this.

Thanks,
--Richard


On Jan 31, 2013, at 2:14 PM, Ryan Sleevi <sleevi@google.com> wrote:

> http://www.w3.org/2012/webcrypto/track/issues/24
> 
> I would like to propose that we CLOSE ISSUE-24.
> 
> There have been no proposals put forth since it was raised.
> 
> Some members have suggested that synchronous methods be permitted on
> the main thread of execution. Implementers objected to this (as, no
> doubt, would the TAG), due to the significant performance concerns
> they introduce. These objections were re-iterated during the TPAC/Lyon
> F2F.
> 
> Further, the transition to a Promises-style API may resolve many of
> the concerns regarding scriptability.
> 
> As such, I propose that this issue be closed.
> 
Received on Monday, 4 February 2013 20:03:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 February 2013 20:03:15 GMT