[Cryptography-dev] Desired API

[Jean-Paul Calderone]

On 07/29/2013 08:13 PM, Alex Gaynor wrote:
> 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?
>
I'm sure that would work.  Please don't count this email as a -anything.

However, `cryptography.encryption´ next to
`cryptography.primitives.encryption´ seems like it's asking for
trouble.  If `cryptography.primitives´ is for things like AES, then how
about `cryptography.primitives.cipher´ instead?  Or perhaps even better,
`cryptography.cipher´.

Also, make sure to pick a convention for singular vs plural.  is it
`primitives´ or `primitive´?  `cipher´ or `ciphers´?  Neither is better,
but mixing them is bad.

Should there be more of an outline for the scope of the project?  That
might guide some of the package organization as well.  I know that some
discussion happened, it might be good to record the outcome somewhere.

Jean-Paul

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20130729/c8836157/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20130729/c8836157/attachment-0001.pgp>