- From: Aymeric Vitte <vitteaymeric@gmail.com>
- Date: Wed, 06 Nov 2013 11:53:29 +0100
- To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <527A1FA9.30802@gmail.com>
As I mentioned in other posts, the Streams API is evolving fast right now (there is a new W3C version and a new WHATWG one), and indeed it's good to have a note in WebCrypto spec so it will support progressive operations when Streams are stable, as I wrote too ideally if a createStream method is feasible the spec should just mention that it supports Streams (notwithstanding next sentence). reuse crypto operations: I suggested a stop/resume method for streams which is different from pause/unpause where resume does restart from a cloned state of the operation that receives stop and handle it as eof (ie cloning the crypto operation and closing the current operation) Regards Aymeric Le 05/11/2013 09:27, GALINDO Virginie a écrit : > > Dear all, > > Please note that the minutes of our previous call are available under > http://www.w3.org/2013/10/28-crypto-minutes.html > > Regards, > > Virginie > > Gemalto > > > ------------------------------------------------------------------------ > This message and any attachments are intended solely for the > addressees and may contain confidential information. Any unauthorized > use or disclosure, either whole or partial, is prohibited. > E-mails are susceptible to alteration. Our company shall not be liable > for the message if altered, changed or falsified. If you are not the > intended recipient of this message, please delete it and notify the > sender. > Although all reasonable efforts have been made to keep this > transmission free from viruses, the sender will not be liable for > damages caused by a transmitted virus -- Peersm : http://www.peersm.com node-Tor : https://www.github.com/Ayms/node-Tor GitHub : https://www.github.com/Ayms
Received on Wednesday, 6 November 2013 10:54:28 UTC