Synced Notification Sync Change Processor

sync/protocol/synced_notification_specifics.proto

Index: sync/protocol/synced_notification_specifics.proto
diff --git a/sync/protocol/synced_notification_specifics.proto b/sync/protocol/synced_notification_specifics.proto
index db82f525ee49b42eb0a102a87235da0c026c47f1..b97f8f336459efcd6a83f5ed71c53ef0025bff68 100644
--- a/sync/protocol/synced_notification_specifics.proto
+++ b/sync/protocol/synced_notification_specifics.proto
@@ -14,7 +14,12 @@ option retain_unknown_fields = true;
 
 package sync_pb;
 
+import "server_render.proto";

[Nicolas Zea, 2013/01/05 01:18:48]

Are you planning to reuse these protos anywhere? If not, I think I'd prefer
having them inlined.

Otherwise, the files should be renamed to make it clearer that they're specifics
to the SyncedNotification datatype. "Server Data" in particular  sounds like it
related to the sync engine.

[Pete Williamson, 2013/01/18 18:58:39]

Yes, these are being matched by a similar set of protos on the server side.

+import "server_data.proto";
+
 // Properties of SyncedNotificationSpecifics objects.
 message SyncedNotificationSpecifics {
-  // TODO(petewil): this is placeholder data, make a real one
+  // The notification from the server
+  // TODO(petewil): is this always coalesced, or sometimes a plain notification?
+  optional CoalescedNotification coalesced_notification = 1;
 }