[omaha] r163 committed - Edited wiki page ServerProtocolV3 through web user interface.

[om...@googlecode.com]

Revision: 163
Author: waf...@google.com
Date: Thu Jun 19 20:28:34 2014 UTC
Log: Edited wiki page ServerProtocolV3 through web user interface.
http://code.google.com/p/omaha/source/detail?r=163

Modified:
/wiki/ServerProtocolV3.wiki

=======================================
--- /wiki/ServerProtocolV3.wiki Wed Jun 18 19:38:43 2014 UTC
+++ /wiki/ServerProtocolV3.wiki Thu Jun 19 20:28:34 2014 UTC
@@ -142,7 +142,7 @@
* `experiments`: A key/value list of experiment identifiers. Experiment
labels are used to track membership in different experimental groups, and
may be set at install or update time. The experiments string is formatted
as a semicolon-delimited concatenation of experiment label strings. An
experiment label string is an experiment name, followed by a '=' character,
followed by an experimental label value. For
example: "crdiff=got_bsdiff;optimized=O3". Default: "".
* `iid`: A GUID that identifies an installation flow. For example, each
download of a product installer is tagged with a unique GUID. Attempts to
install using that installer can then be grouped. A client SHOULD NOT
persist the iid GUID after the installation flow of a product is complete.
* `installage`: The number of PST8PDT calendar days since the app was
first installed. The first communication to the server should use a special
value of "-1". Compatible clients MAY fuzz this value to the week
granularity (e.g. send "0" for 0 through 6, "7" for 7 through 13, etc).
Default: "0"
- * `installdate`: The date-based counting equivalent of installage: this
is a numeric calendar day that the app was installed on. (This value is
provided by the server in the response to the first request in the
installation flow. See [#Date_Based_Counting]) The first communication to
the server should use a special value of "-1". A value of "-2" indicates
that this value is not known. Default: "-2".
+ * `installdate`: The date-based counting equivalent of installage: this
is a numeric calendar day that the app was installed on. (This value is
provided by the server in the response to the first request in the
installation flow. See [#Client-Regulated_Counting_(Date-Based)]) The first
communication to the server should use a special value of "-1". A value
of "-2" indicates that this value is not known. Default: "-2".
* `installsource`: A string indicating the cause of this install or
update flow. As examples: "organic" indicating an organic web
download, "scheduler" indicating a scheduled update, "ondemand" indicating
a user-prompted update. Default: "".
* `tag`: An field for a client to transmit arbitrary update parameters
in string form. Compatible clients and servers MAY use this attribute to
negotiate special update rules. Alternatively, they MAY extend the protocol
to represent the information more clearly in another parameter. As an
example, Omaha Client uses this field to transmit whether a Google Chrome
installation is on the "stable", "dev", or "beta" channel, which affects
how the server issues update responses for that installation. Default: "".
* `fingerprint`: If there is only one package, the fingerprint for that
package may be transmitted at the `<app>` level. See
[#Packages_&_Fingerprints]. Default: "".