State should not depend on the API server

[David Cheney]

The goal I have been tasked with is breaking the interdependency
between the state package and the _client_ api types in
state/api/params.

I don't have any opinion on adding additional layers assuming that
their dependancies flow downwards, ie

labix.org/mgo <- juju/state <- juju/apiserver

On Mon, Sep 1, 2014 at 4:03 PM, John Meinel <john at arbash-meinel.com> wrote:
> FWIW I'd favor 3 layers, though it does mean you have to do copying between
> structs that would likely otherwise be almost identical. A State layer for
> saving in the DB, an API layer for communication, and a Model layer for use
> in the Agents/Clients.
>
> John
> =:->
>
>
>
> On Mon, Sep 1, 2014 at 9:40 AM, David Cheney <david.cheney at canonical.com>
> wrote:
>>
>> Hello,
>>
>> This is an introductory email to explain my upcoming series of pull
>> requests.
>>
>> The theme is simple: state must not depend on the api server.
>>
>> This is currently not true, state depends on api/params because some
>> of the api types have leaked into the state package and are being
>> directly stored in mongo.
>>
>> Please speak up if you disagree with this proposal.
>>
>> Dave
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>