W3C home > Mailing lists > Public > public-webcrypto@w3.org > August 2012

Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API]

From: Ryan Sleevi <sleevi@google.com>
Date: Mon, 27 Aug 2012 16:13:55 -0700
Message-ID: <CACvaWvZF9Csqdb4Rtygv+6kXWc=D-6DW8OoRMzFjjFLxmrNi0g@mail.gmail.com>
To: Mark Watson <watsonm@netflix.com>
Cc: Arun Ranganathan <arun@mozilla.com>, Web Cryptography Working Group <public-webcrypto@w3.org>
On Tue, Aug 21, 2012 at 1:28 PM, Mark Watson <watsonm@netflix.com> wrote:
> So how are applications supposed to do 'clean-up' operations that may require server communication, for example ?
> There seems to be an assumption that the negative user experience when it takes a window a short time to close is worse than the negative user experience that might result from applications not being able to perform a clean close operation. Not sure how you could conclude that without knowledge of the applications….
> …Mark

To loop in other participants on the discussion - Mark has raised this
discussion point on the WHATWG mailing list.

Relevant archive links for those not subscribed:
- http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-August/036964.html
- http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-August/036969.html

Outside of the use case Mark described, I think running synchronous
operations on the main thread is going to be problematic.
Received on Monday, 27 August 2012 23:14:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:01:26 UTC