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

Re: JS code examples for ACTION 43

From: David Dahl <ddahl@mozilla.com>
Date: Thu, 6 Sep 2012 10:18:12 -0700 (PDT)
To: Wan-Teh Chang <wtc@google.com>
Cc: "public-webcrypto@w3.org Working Group" <public-webcrypto@w3.org>, Ryan Sleevi <sleevi@google.com>
Message-ID: <2116959028.887416.1346951892522.JavaMail.root@mozilla.com>
----- Original Message -----
> From: "Wan-Teh Chang" <wtc@google.com>
> To: "Ryan Sleevi" <sleevi@google.com>
> Cc: "David Dahl" <ddahl@mozilla.com>, "public-webcrypto@w3.org Working Group" <public-webcrypto@w3.org>
> Sent: Thursday, September 6, 2012 12:03:29 PM
> Subject: Re: JS code examples for ACTION 43

> > [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.

I see. Do we need to specify a new event?
Received on Thursday, 6 September 2012 17:18:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 6 September 2012 17:18:44 GMT