[Cryptography-dev] Desired API

[Alex Gaynor]

So my idea is that we have something like:

cryptography.c -> contains all teh cffi crap
cryptography.primitives.* -> contains low level algorithms for example:
   cryptography.primtives.encryption.aes -> implementation of AES
cryptography.* -> contains high level recipes, for example:
   cryptography.encryption: contains a thing which takes an encryption
algorithm and a hasher and and does the right thing.

What do people think?

Alex



On Mon, Jul 29, 2013 at 4:27 PM, Donald Stufft <donald at stufft.io> wrote:

> So now that this mailing list is a thing, let's have a discussion!
>
> What do we want the desired API to look like? Probably exposing
> both low and high level (starting with low)? How should we
> properly separate the two API's in the code in order to have a
> clear delineation between the two target audiences.
>
> I dunno I'm just spit balling to get things started :)
>
> -----------------
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
> DCFA
>
>
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> http://mail.python.org/mailman/listinfo/cryptography-dev
>
>


-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20130729/c15a3fd9/attachment.html>