- From: Aymeric Vitte <vitteaymeric@gmail.com>
- Date: Tue, 29 Jan 2013 11:21:27 +0100
- To: Ryan Sleevi <sleevi@google.com>, ddahl@mozilla.com
- CC: public-webcrypto-comments@w3.org
Le 28/01/2013 22:56, Ryan Sleevi a écrit : >>> 7) You make use of DOMString in the following methods: >>> >> a) encryptAndSign (aPlainText) >>> >> b) protect (aPlaintext) >>> >> c) unprotect (aPlaintext - see 5) >>> >> d) sign (aClearData) >>> >> e) verify (aDataToVerify) >>> >>How is this data supposed to be canonicalized? How is arbitrary >>> >>binary >>> >>data supposed to be encoded? What about decoded? >> > >> >While I would like to make the interface as simple as possible (using strings), this is an issue that may require the use of ArrayBufferViews after all. I am unsure how to make DOMStrings viable here. > http://encoding.spec.whatwg.org/ ? > If this can help, simple example here (https://github.com/Ayms/node-typedarray) how to use ArrayBuffers, TextEncoder/Decoder, and make all this more "high-level". -- 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 Tuesday, 29 January 2013 10:19:45 UTC