Re: crypto-ISSUE-37: Method naming [Web Cryptography API] from Wan-Teh Chang on 2012-08-30 (public-webcrypto@w3.org from August 2012)

From: Wan-Teh Chang <wtc@google.com>
Date: Thu, 30 Aug 2012 10:09:42 -0700
To: Ryan Sleevi <sleevi@google.com>
Cc: Arun Ranganathan <arun@mozilla.com>, David Dahl <ddahl@mozilla.com>, Web Cryptography Working Group <public-webcrypto@w3.org>
Message-ID: <CALTJjxFZpPKaH7SDoOPX1JFooqgg3f9zYPr2Hac2hoHFh-9=yg@mail.gmail.com>

On Wed, Aug 29, 2012 at 8:01 PM, Ryan Sleevi <sleevi@google.com> wrote:
>
> What I dislike about 3 is that it implies a class hierarchy, of which
> JavaScript isn't really class-based (it's prototype). It also introduces a
> number of objects into global scope.
>
> Maybe
>
> var e = window.crypto.Encryptor(...) ?

Yes, I've been assuming these are under window.crypto, otherwise the
name "Verifier" would be too vague.

Wan-Teh

Received on Thursday, 30 August 2012 17:10:12 UTC