On 29 July 2014 18:12, William Reade <william.re...@canonical.com> wrote: > On Tue, Jul 29, 2014 at 6:57 PM, roger peppe <rogpe...@gmail.com> wrote: >> >> On 29 July 2014 16:50, Eric Snow <eric.s...@canonical.com> wrote: >> > The API server side of backup made it into 1.20 (the client-side and >> > CLI did not). However, the API is exposed via HTTP POST rather than >> > through websockets RPC. >> >> An HTTP POST request seems about right for a call that >> streams a significant amount of data. Is there any particular >> reason this has to change? > > > It's not what we discussed and agreed in vegas; and, crucially, it fails to > make previously-made backups available from any state server. We want WS > APIs for creating, listing, and deleting backups; and, yes, we want to > *download* those backups over HTTP, and the CLI will be creating them, > waiting for them to be ready, and then downloading them over HTTP. But a > POST to just create-a-backup-and-download-it-and-forget-about-it is not what > we want or need.
OK, that seems fine. Thanks for the clarification. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
