crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API]

crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API]

http://www.w3.org/2012/webcrypto/track/issues/22

Raised by: Ryan Sleevi
On product: Web Cryptography API

Some members have expressed a desire to have CryptoOperation objects be clone-able, so that the same operation may be re-used for multiple data streams, without affecting the state of the original object.

var a = /* create a CryptoOperation */;
var b = a.clone();  // Creates a new, independent CryptoOperation

The outstanding questions are:
1) Is there consensus to support a clone() method?
2) If so, what are the use cases for such a method?
3) Is clone() a synchronous or asynchronous operation?
4) What are the expected differences between clone() and creating a new object with the same parameters and key(s)?
5) Is this clone() method part of the structured clone algorithm, or is it independent?
6) If an object is cloned, are the callbacks cloned or reset?
7) In what states is it valid to clone an object?

Received on Monday, 20 August 2012 14:19:20 UTC