ISSUE-22: Should CryptoOperations be clonable

Should CryptoOperations be clonable

State:

CLOSED

Product:

functional for Web Crypto API

Raised by:

Ryan Sleevi

Opened on:

2012-08-20

Description:

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?

Related Actions Items:

No related actions

Related emails:

1. ISSUE-22 (from vitteaymeric@gmail.com on 2013-11-14)
2. Re: On a Futures-style API (from sleevi@google.com on 2013-04-24)
3. Re: On a Futures-style API (from vitteaymeric@gmail.com on 2013-04-24)
4. Re: On a Futures-style API (from slightlyoff@google.com on 2013-04-24)
5. Re: On a Futures-style API (from vitteaymeric@gmail.com on 2013-04-24)
6. Re: On a Futures-style API (from sleevi@google.com on 2013-04-23)
7. W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-04-12)
8. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from vitteaymeric@gmail.com on 2013-04-04)
9. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from watsonm@netflix.com on 2013-04-04)
10. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from vitteaymeric@gmail.com on 2013-04-04)
11. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from vitteaymeric@gmail.com on 2013-04-04)
12. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from watsonm@netflix.com on 2013-04-04)
13. Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from vitteaymeric@gmail.com on 2013-04-04)
14. [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (from Virginie.GALINDO@gemalto.com on 2013-04-04)
15. RE: ISSUE 22 - Re: Incomplete blocks (from Virginie.GALINDO@gemalto.com on 2013-02-26)
16. Re: ISSUE 22 - Re: Incomplete blocks (from sleevi@google.com on 2013-02-25)
17. RE: ISSUE 22 - Re: Incomplete blocks (from Virginie.GALINDO@gemalto.com on 2013-02-25)
18. Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from wtc@google.com on 2012-08-28)
19. RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-28)
20. RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from Asad.Ali@gemalto.com on 2012-08-27)
21. W3C Web Crypto WG - agenda for 27th of august call - today (from Virginie.GALINDO@gemalto.com on 2012-08-27)
22. RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-08-27)
23. Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from wtc@google.com on 2012-08-23)
24. [W3C Web Crypto WG] functional features list in draft API and issue tracker (from Virginie.GALINDO@gemalto.com on 2012-08-22)
25. Re: [W3C Web Crypto WG] functional features list in draft API and issue tracker (from sleevi@google.com on 2012-08-21)
26. [W3C Web Crypto WG] functional features list in draft API and issue tracker (from Virginie.GALINDO@gemalto.com on 2012-08-21)
27. Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from ddahl@mozilla.com on 2012-08-20)
28. Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from sleevi@google.com on 2012-08-20)
29. crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-20)

Related notes:

Display change log