So as discussed, I think we still want to support a HTTP GET based API for actually downloading the content to the client. And the CLI can do steps like: RPC to a request to create a backup (either this is synchronous and returns a URL, or the next step is to wait on the next request for when it is done to get the URL) HTTP GET to download the backup .tar (.xz,,bz2,gz whatever) put those bytes somewhere locally and then exit.
John =:-> On Wed, Jul 30, 2014 at 6:24 AM, Menno Smits <[email protected]> wrote: > >> But I'm a bit suspicious... would someone please confirm that we don't >> have *any* released clients that use the POST API? The above is predicated >> on that assumption. >> > > The juju command line client hasn't yet seen changes to call the backup > POST API. The work was seemingly being done "server first, then client" > (which seem logical) and the client work didn't make the release (and isn't > done even today). > > IMHO, Eric's proposal seems totally fine to me. > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
