Splitting out state/api into its own repo

[Eric Snow]

On Fri, Jun 27, 2014 at 3:31 AM, roger peppe <roger.peppe at canonical.com> wrote:
> Likewise the client side code can be automatically generated
>  (I have done that before too), which would make for a Go
> API interface which exactly reflected the server side.

Is that true of AddLocalCharm(), UploadTool(), and WatchDebugLog()?
(in state/api/client.go)  The first two send a compressed file as part
of their request (so they use raw HTTP requests for RPC) and the last
one uses websockets directly to stream back a running log.

-eric