Mutability of CryptoOperationData

As SubtleCrypto functions take sequences of typed arrays, what is the intended semantics in the case the arrays are mutated while an operation is underway? Are implementors expected to copy the data (or mark it for copy on write)?

One way to solve this in a simple and efficient way would be to specify that the operations implicitly freeze the typed arrays passed to them. As far as I can tell, this should be just fine for all use cases - e.g. one is unlikely to modify data they just signed.

- WBR, Alexey Proskuryakov

Received on Friday, 25 October 2013 19:33:55 UTC