First step at synchronizing client model changes with service.

mojo/services/public/interfaces/view_manager/view_manager.mojom

Index: mojo/services/public/interfaces/view_manager/view_manager.mojom
diff --git a/mojo/services/public/interfaces/view_manager/view_manager.mojom b/mojo/services/public/interfaces/view_manager/view_manager.mojom
index 673068cc1a457b773f9052868cdcf7db634aac6b..a467ce0a738f4b40b0dfcbbe2707a0f5a8469673 100644
--- a/mojo/services/public/interfaces/view_manager/view_manager.mojom
+++ b/mojo/services/public/interfaces/view_manager/view_manager.mojom
@@ -15,8 +15,8 @@ module mojo.services.view_manager {
 // uint16 as the connection id of the originating connection is used.
 //
 // The root node is identified with a connection id of 0, and value of 1.
-[Peer=ViewManagerClient]
-interface ViewManager {
+[Peer=IViewManagerClient]
+interface IViewManager {

[sky, 2014/04/28 23:04:19]

Sadness.

[Ben Goodger (Google), 2014/04/29 00:00:54]

:D

   // Creates a new node with the specified id. It is up to the client to ensure
   // the id is unique to the connection (the id need not be globally unique).
   CreateNode(uint16 node_id) => (bool success);
@@ -43,8 +43,8 @@ interface ViewManager {
   SetView(uint32 node_id, uint32 view_id, int32 change_id) => (bool success);
 };
 
-[Peer=ViewManager]
-interface ViewManagerClient {
+[Peer=IViewManager]
+interface IViewManagerClient {
   // Invoked once the connection has been established. |connection_id| is the id
   // used to uniquely identify the connection.
   OnConnectionEstablished(uint16 connection_id);