drive: Apps.delete returns HTTP_NO_CONTENT on success.

drive: Apps.delete returns HTTP_NO_CONTENT on success.

The status code is consistent with other methods like Files.delete,
so we should better align to it. This CL fixes the return code
assumption in DriveAppRegistry that previously expected HTTP_SUCCESS.

BUG=324166
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245295

[hashimoto, 2014-01-16 04:37:25]

lgtm

https://codereview.chromium.org/140533002/diff/20001/chrome/browser/drive/dri...
File chrome/browser/drive/drive_app_registry.h (right):

https://codereview.chromium.org/140533002/diff/20001/chrome/browser/drive/dri...
chrome/browser/drive/drive_app_registry.h:55: // Callback type for
UninstallApp(). Returns HTTP_NO_CONTENT on success.
nit: I guess UninstallApp's function comment should be a better place to put
this.

[kinaba, 2014-01-16 04:47:35]

https://codereview.chromium.org/140533002/diff/20001/chrome/browser/drive/dri...
File chrome/browser/drive/drive_app_registry.h (right):

https://codereview.chromium.org/140533002/diff/20001/chrome/browser/drive/dri...
chrome/browser/drive/drive_app_registry.h:55: // Callback type for
UninstallApp(). Returns HTTP_NO_CONTENT on success.
On 2014/01/16 04:37:25, hashimoto wrote:
> nit: I guess UninstallApp's function comment should be a better place to put
> this.

Done.

[commit-bot: I haz the power, 2014-01-16 04:49:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kinaba@chromium.org/140533002/120001

[commit-bot: I haz the power, 2014-01-16 19:55:12]

Change committed as 245295