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

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

From: Alex Russell <slightlyoff@google.com>
Date: Thu, 31 Jan 2013 14:23:19 -0500
Message-ID: <CANr5HFUu765HDYnkRsOEt_dJXvNNT4p3a7axSqyoEq2g+X88OA@mail.gmail.com>
To: Ryan Sleevi <sleevi@google.com>
Cc: public-webcrypto@w3.org
I, for one, would object to a stuck l synchronous API and therefore support
closing this issue.
On Jan 31, 2013 2:15 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 Thursday, 31 January 2013 19:23:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 January 2013 19:23:47 GMT