- From: Ryan Sleevi <sleevi@google.com>
- Date: Thu, 7 Mar 2013 09:26:21 -0800
- To: Aymeric Vitte <vitteaymeric@gmail.com>
- Cc: Mark Watson <watsonm@netflix.com>, public-webcrypto-comments@w3.org, Harry Halpin <hhalpin@w3.org>
On Thu, Mar 7, 2013 at 9:14 AM, Aymeric Vitte <vitteaymeric@gmail.com> wrote: > > Le 07/03/2013 16:39, Ryan Sleevi a écrit : > >> >> You don't freeze. You can't. You copy. This is already reflected in a >> number of APIs - including ArrayBuffer itself. >> >> This is not anything new that I am proposing here. >> > OK, indeed it's in the ArrayBuffer spec, would you have an API example for > ABV cloning? I don't understand what you're asking. TypedArrays make it clear how to create another ABV. The normative text requirement is simply that it be equivalent to copying the bytes - that is, that the state of the data at the time of the call is the data that is encrypted, regardless of further modifications that may occur to the data after the return and before the asynchronous completion. The entire point is to avoid specifying "You must copy this data" - since an implementation should be free to do any number of optimizations that may allow it to avoid copying (eg: copy on write). The spec does not need to say that though - all that matters is the observed behaviour. > > > -- > jCore > Email : avitte@jcore.fr > iAnonym : http://www.ianonym.com > node-Tor : https://www.github.com/Ayms/node-Tor > GitHub : https://www.github.com/Ayms > Web : www.jcore.fr > Webble : www.webble.it > Extract Widget Mobile : www.extractwidget.com > BlimpMe! : www.blimpme.com >
Received on Thursday, 7 March 2013 17:26:49 UTC