summaryrefslogtreecommitdiffstats
path: root/sync
diff options
context:
space:
mode:
authorpvalenzuela@chromium.org <pvalenzuela@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-09-07 07:20:00 +0000
committerpvalenzuela@chromium.org <pvalenzuela@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-09-07 07:20:00 +0000
commit5ef4265b7edbcb5b96a4d690312103f37b986afc (patch)
treed01ece8ac45791474cfcd611cf0031ea25e2ce8f /sync
parentdc8ec3f4e773a5444ee6edaf4e7cda1a1d273ad0 (diff)
downloadchromium_src-5ef4265b7edbcb5b96a4d690312103f37b986afc.zip
chromium_src-5ef4265b7edbcb5b96a4d690312103f37b986afc.tar.gz
chromium_src-5ef4265b7edbcb5b96a4d690312103f37b986afc.tar.bz2
Update client-side sync.proto file so that it is in sync with the
server-side version BUG= Review URL: https://chromiumcodereview.appspot.com/23985004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221910 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync')
-rw-r--r--sync/protocol/sync.proto33
1 files changed, 29 insertions, 4 deletions
diff --git a/sync/protocol/sync.proto b/sync/protocol/sync.proto
index b89b9b7..445fa41 100644
--- a/sync/protocol/sync.proto
+++ b/sync/protocol/sync.proto
@@ -590,6 +590,12 @@ message AuthenticateMessage {
required string auth_token = 1;
};
+message ClearUserDataMessage {
+};
+
+message ClearUserDataResponse {
+};
+
// The client must preserve, store, and resend the chip bag with
// every request. The server depends on the chip bag in order
// to precisely choreograph a client-server state machines.
@@ -637,8 +643,7 @@ message ClientToServerMessage {
optional AuthenticateMessage authenticate = 6;
// Request to clear all Chromium data from the server.
- // DEPRECATED - this field was never used in production.
- // optional ClearUserDataMessage clear_user_data = 9;
+ optional ClearUserDataMessage clear_user_data = 9;
optional string store_birthday = 7; // Opaque store ID; if it changes, duck!
// The client sets this if it detects a sync issue. The server will tell it
@@ -668,6 +673,27 @@ message ClientToServerMessage {
optional string invalidator_client_id = 14;
};
+// This request allows the client to convert a specific crash identifier
+// into more general information (e.g. hash of the crashing call stack)
+// suitable for upload in an (authenticated) DebugInfo event.
+message GetCrashInfoRequest {
+ // Id of the uploaded crash.
+ optional string crash_id = 1;
+
+ // Time that the crash occurred.
+ optional int64 crash_time_millis = 2;
+}
+
+// Proto to be written in its entirety to the debug info log.
+message GetCrashInfoResponse {
+ // Hash of the crashing call stack.
+ optional string stack_id = 1;
+
+ // Time of the crash, potentially rounded to remove
+ // significant bits.
+ optional int64 crash_time_millis = 2;
+}
+
message CommitResponse {
enum ResponseType {
SUCCESS = 1;
@@ -836,8 +862,7 @@ message ClientToServerResponse {
optional ClientCommand client_command = 7;
optional ProfilingData profiling_data = 8;
- // DEPRECATED - this field was never used in production.
- // optional ClearUserDataResponse clear_user_data = 9;
+ optional ClearUserDataResponse clear_user_data = 9;
optional GetUpdatesMetadataResponse stream_metadata = 10;
// If GetUpdatesStreamingResponse is contained in the ClientToServerResponse,
// none of the other fields (error_code and etc) will be set.