Organising apiserver facades

[Menno Smits]

On 9 July 2017 at 18:13, roger peppe <rogpeppe at gmail.com> wrote:

> Getting all of that facade-specific logic out of the apiserver package
> seems like a great idea to me. I don't think it would take *too* much work
> to factor the helper logic into its own package entirely, with no
> dependencies on the facades.
>



> The client is actually almost there already with its APICaller interface
> as common currency - we should really follow the intent of this old
> comment of William's
> <https://github.com/juju/juju/blob/develop/api/interface.go#L285-L289>.The
> manifold issue is the interesting one - work out a good solution to that
> and the rest'll come quite quickly, I feel.
>

​FWIW, that list of client side facade factory methods on api.Connection
which shouldn't be there used to be a lot bigger. We've removed about two
thirds of them while converting the machine agent to use the dependency
engine.


>
> It would be marvellous to get parts moving more freely in Juju again -
> losing big fan-out dependency graphs is a good way to move in that
> direction, I'm pretty sure.
>

​+1

- Menno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20170710/64069b22/attachment.html>