aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay Buffington>
Subject Re: Handling of aurora update when job/task cannot be scheduled
Date Tue, 20 May 2014 18:41:05 GMT
On Tue, May 20, 2014 at 9:14 AM, Mark Chu-Carroll <>wrote:

> I agree. At the moment, the update process is completely driven by the
> client, which creates some odd usability issues.


If we ran updates primarily on the server, they could be handled
> asynchronously or synchronously in a way consistent with create, by using
> wait-until parameters.

Why are updates driven by the client?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message