The idea is that the charm store is growing a lot since the original api was done. It's gaining a first class entity in bundles, it'll be growing identity support, search functionality, and other metadata. The api space is growing and needs to be able to be consistent with other tools as they're pulled together to provide a single JAAS api.
Now is a good time to revisit how the api would look today if we knew then what we all know now and see coming. The work here is meant to bring together the apis of the store, charmworld, and future tasks. We appreciate feedback in making it the best and most clear api we can put together that can stand up to the next years of work. Rick On Wed, 09 Jul 2014, Gustavo Niemeyer wrote: > Is there a reason to reinvent the API from the ground up, instead of > extending what exists today? > > On Mon, Jul 7, 2014 at 6:14 AM, roger peppe <rogpe...@gmail.com> wrote: > > Francesco Banconi and I have produced a possible specification for the > > new charm store API, combining features from the existing charm store > > API and the charmworld API. > > > > Please take a look and see if it correlates reasonably with your own needs. > > > > https://docs.google.com/a/canonical.com/document/d/1ILHRpOe-qDlmjxHBbLUea7InDpehx5_roJ1ynZmcZDc > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
