Proposed new charm store API

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-07-09 11:16 AM, roger peppe wrote:
> If we need to provide backward compatibility, we could do that in a
> separate name space without changing the proposed API.

The existing charm-events endpoint requires a revision-id, so it will
not work when uploads are done directly instead of being ingested from
a VCS.  Similarly, the "digest" field of charm-info would not be possible.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTvV6RAAoJEK84cMOcf+9h0D0H/A6zOWDlWqZ1Zq4EMfdYODhV
dOMC8f23MEGile29hA48J2ElIA6s2YmHnlt+t7H1N8xyoMnKbejMoGE/8v7FMRTk
QaGBlr6XlLX/TWxyDpzjlW4oZQ5oUSsF+ofVRsoXfsfz0Id67uaNpOW/mPdwNI1h
YQfaXWdZ4NE1rdNLT3IwDU/QRX+gUbe3ZsdhbuJIaM5dF2Wxqx5f+Zq7+nKEu18H
yq76iL+WmAiUNnLJdIbqlSUTfI10HAJJQQLveruj04dd5wy/cpXmvIaK3vwrRS7U
W+kto1/7rYTkqMhVeXKfpogXfORSWmBAVAHkHClzEa8ujUAoSFXCN+rYKfKGYjA=
=Y3AZ
-----END PGP SIGNATURE-----