Add calls to the server to request WebAPK updates.

chrome/browser/android/webapk/webapk.proto

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package webapk;
 
 // Creates a WebAPK on the server and returns URL to download WebAPK from Google
 // Play.
 message CreateWebApkRequest {
   optional WebApk webapk = 1;
 }
 
-// Response to CreateWebApkRequest.
-message CreateWebApkResponse {
+// Creates a updated WebAPK on the server and returns URL to download WebAPK
+// from Google Play.
+message UpdateWebApkRequest {
+  optional WebApk webapk = 1;
+}
+
+// Response after creating or updating a WebAPK.
+message WebApkResponse {

[pkotwicz, 2016/08/02 21:05:04]

I think that we should either:
- Have a different "create WebAPK proto" and a different "update WebAPK" proto
and have a different "create WebAPK response" proto and a different "update
WebAPK response" proto

OR

- Have the same proto for "Creating WebAPKs" and for "Updating WebAPKs" and have
the same proto for the "Create WebAPK response" and for the "Update WebAPK
response"

[Xi Han, 2016/08/03 17:30:05]

As discussed offline, just keep the proto the same as what the server declared.

   // Package name to install WebAPK at.
   optional string webapk_package_name = 1;
 
-  // URL to download WebAPK.
-  optional string signed_download_url = 2;
+  // Version code of the WebAPK.
+  optional string version = 2;
+
+  // URL to download WebAPK from Google Play.
+  optional string signed_market_url = 5;

[pkotwicz, 2016/08/03 01:07:06]

In the new world, Chrome is responsible for downloading the WebAPK not the
Google Play server. In this new world, I think that |signed_download_url| makes
more sense than |signed_market_url|

Yes, the name of the field on the server needs to be updated

[Xi Han, 2016/08/03 17:30:05]

Done.

+
+  // Warnings regarding the creation or update of the WebAPK, if any.
+  repeated string warnings = 4;

[pkotwicz, 2016/08/03 01:07:06]

We do not seem to be using this field. Let's skip it for now and use the
|reserved| keyword

[Xi Han, 2016/08/03 17:30:04]

Done.

 }
 
 message WebApk {
+  // Package name of the WebAPK.
+  optional string package_name = 1;
+
+  // Version code of the WebAPK.
+  optional string version = 2;

[pkotwicz, 2016/08/02 21:05:04]

You do not seem to send this field in webapk_installer.cc

[Xi Han, 2016/08/03 17:30:05]

Good catch, added.

+
   // The URL of the Web App Manifest.
-  optional string manifest_url = 2;
+  optional string manifest_url = 3;
 
   // Chrome's package name.
-  optional string requester_application_package = 4;
+  optional string requester_application_package = 5;
 
   // Chrome's version.
-  optional string requester_application_version = 5;
+  optional string requester_application_version = 6;
 
   // The Web App Manifest.
-  optional WebAppManifest manifest = 6;
+  optional WebAppManifest manifest = 7;
 
-  reserved 1, 3, 7;
+  reserved 4;
 }
 
 // Contains data from the Web App Manifest.
 message WebAppManifest {
   optional string name = 1;
   optional string short_name = 2;
   optional string start_url = 4;
   repeated string scopes = 5;
   repeated Image icons = 6;
   optional string orientation = 9;
@@ skipping 11 matching lines @@
   // MD5 hash of the icon's bytes. There should not be any transformations
   // applied to the icon's bytes prior to taking the MD5 hash.
   optional string hash = 5;
 
   // Actual bytes of the image. This image may be re-encoded from the original
   // image and may not match the MD5 hash field above.
   optional bytes image_data = 6;
 
   reserved 2 to 4;
 }