W3C home > Mailing lists > Public > public-webcrypto@w3.org > February 2013

Missing InvalidStateError when calling the CryptoOperation methods in an 'incorrect' order?

From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Date: Thu, 28 Feb 2013 14:52:40 +0000
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <E46FB6E1-BAAE-4CF2-A184-049B0AAFBFF0@inventivegroup.com>
All,

I have a couple extra question related to 'error' conditions when calling the CryptoOperation methods in an 'incorrect' order.

Shouldn't finish throw an InvalidStateError when it is called after the abort() method is called? The abort method doesn't sets the internal state to error because it is probably not an error to call abort multiple times on the same operation? If calling abort multiple times on the same operation is valid I think that an extra internal state 'abort' is required.

The process method has the same issue, calling process() after abort() should probably also throw an InvalidStateError.

Kind regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 425 41 02
Office fax: +32 3 821 01 71
nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com>
www.inventivedesigners.com


[cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110]


________________________________

Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer



image001.png
(image/png attachment: image001.png)

image002.png
(image/png attachment: image002.png)

image003.png
(image/png attachment: image003.png)

Received on Thursday, 28 February 2013 14:53:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 February 2013 14:53:13 GMT