- From: Wan-Teh Chang <wtc@google.com>
- Date: Thu, 6 Sep 2012 10:03:29 -0700
- To: Ryan Sleevi <sleevi@google.com>
- Cc: David Dahl <ddahl@mozilla.com>, "public-webcrypto@w3.org Working Group" <public-webcrypto@w3.org>
On Wed, Sep 5, 2012 at 5:33 PM, Ryan Sleevi <sleevi@google.com> wrote: > > You are correct that the spec, in discussing the internal state of the > object, requires that the state transition be complete before calling > the next method (Step 1 of init/processData/complete). That is, in > order for processData() to not fail, the "state" must be "processing" > [1], which is only set AFTER init() has asynchronously completed. [...] > [1] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#dfn-CryptoOperation-state-processing I see. It is also not clear to me whether an application can call processData() or complete() before a previous processData() call has asynchronously completed. The spec allows that. In fact, there is no event that indicates the completion of a processData() call. The |progress| event is fired only if the processData() call resulted in output. Wan-Teh
Received on Thursday, 6 September 2012 17:04:08 UTC