Lines Matching full:server
5 // Sync protocol for communication between sync client and server.
84 // Server implementations are obligated to preserve the contents of
87 // to update the server.
125 // client-generated ID. If the commit succeeds, the server will generate
128 // |id_string| is always the server generated ID. The original
136 // in the message. In all other situations, it is a server ID.
140 // old_parent_id is only set in commits and indicates the old server
147 // maintained by for each item. If zero in a CommitMessage, the server
149 // new server ID and an initial version number. If nonzero in a
151 // the server will use |id_string| to locate the item. Then, if the item's
152 // current version on the server does not match |version|, the commit will
153 // fail for that item. The server will not update it, and will return
171 // Before then, server implementations would maintain a unique-within-parent
186 // this item was last updated on the server. This is now equivalent
192 // instanced item. The server ensures that there is never more
198 // This variant of the tag is created by the server, so clients can't create
314 // per account. The server will enforce uniqueness on this tag
319 // client_defined_unique_tag is the creator of the entity. Server defined
320 // tags are entities created by the server at account creation,
325 // b) Server tag - If server committed the item as unique
338 // by |unique_position| before either the client or server made much of an
395 // The configuration of this client at commit time. Used by the server to
397 // involve server-side interaction, and e.g require explicit user intent for
409 // that the server may interpret as a hint about the location of the latest
413 // name defined in the progress marker, but the client and server should
424 // This flag is set if the invalidation server reports that it may have
426 // locally cached hints that are older than the server-did-drop notification.
437 // - The client's connection to the invalidation server is currently or
472 // field numbers of all EntitySpecifics fields supported by the server.
476 // An opaque-to-the-client sequence of bytes that the server may interpret
480 // value previously returned by the server in an earlier GetUpdatesResponse.
483 // The opaque semantics of this field are to afford server implementations
485 // a server implementation built on top of a distributed storage service --
489 // possible if the server is allowed to embed arbitrary information in
492 // Server implementations should keep the size of these tokens relatively
494 // regardless of the number of items synchronized. (A possible bad server
501 // token mechanism can set this field in a GetUpdatesMessage. The server
507 // that the server may interpret as a hint about the location of the latest
544 // event, the server will return items of all the indicated types.
551 // The server may opt to return fewer updates than this amount, but it should
555 // Per-datatype progress marker. If present, the server will ignore
571 // Whether the client needs the server to provide an encryption key for this
594 // every request. The server depends on the chip bag in order
595 // to precisely choreograph a client-server state machines.
600 // If the server does not return a chip bag, the client must assume
605 // processes the response from the server.
607 // Server chips are deliberately oqaque, allowing the server
617 // The server should attempt to resolve any hierarchy conflicts when this flag
639 // Request to clear all Chromium data from the server.
644 // The client sets this if it detects a sync issue. The server will tell it
653 // Per-client state for use by the server. Sent with every message sent to the
654 // server.
661 // The client should set this on every message sent to the server, though its
665 // The ID that our invalidation client used to identify itself to the server.
666 // Sending the ID here allows the server to not send notifications of our own
694 // client would attempt to honor this position, but nowadays the server
702 // Allows the server to move-aside an entry as it's being committed.
713 // Last modification time (in java time milliseconds). Allows the server
723 // If there are more changes on the server that weren't processed during this
733 // DEPRECATED FIELD - server does not set this anymore.
737 // If present and zero, this estimate is firm: the server has no changes
744 // in this field, and present them back to the server to indicate the
750 // The server may provide a new progress marker even if this is the end of
751 // the batch, or if there were no new updates on the server; and the client
752 // must save these. If the server does not provide a |new_progress_marker|
764 // the server has updated the set of encryption keys (e.g. due to a key
808 // Deprecated. Remove this from the server side.
826 // TRANSIENT_ERROR is not supported. Instead, the server sends back a HTTP
832 // is meaningless to this server. This happens most typically when
