- From: Ryan Sleevi <sleevi@google.com>
- Date: Sat, 7 Sep 2013 19:27:29 -0700
- To: Jim Schaad <ietf@augustcellars.com>
- Cc: public-webcrypto@w3.org
- Message-ID: <CACvaWvavtBO7ZwgYUz67n7gi6yMFkMuva618u9FqK2YeYc7heg@mail.gmail.com>
This was covered on the call. The minutes from two meetings ago (if I recall correctly) should have them. The broader discussion of partial output interfaces (such as the File API) and Streams (MSE, Streams API, ProgressPromise, etc) is happening in WebApps and you can follow there to understand the broader arguments - and concerns - of such interfaces. The minutes should include the discussion as well, as they were discussed on the call. However, I haven't checked. On Sep 7, 2013 7:23 PM, "Jim Schaad" <ietf@augustcellars.com> wrote: > I was just going through the Editor’s draft dated 30 August 2013 and was > shocked to find that there is no longer a definition of the CryptoOperation > interface in the document. Instead a sequence of CryptoOperationData > objects are passed into the root call. **** > > ** ** > > I do however note that the excising was not complete as it is still > included in the verify method description.**** > > ** ** > > I completely missed the reasoning behind this. When was this discussed > either on the mailing list or in a telechat so I can go back and find the > justification/reasoning behind it.**** > > ** ** > > Jim**** > > ** ** >
Received on Sunday, 8 September 2013 02:27:57 UTC