summaryrefslogtreecommitdiffstats
path: root/chrome/browser/sync/protocol
Commit message (Collapse)AuthorAgeFilesLines
* Revert my revert because it causes more problems.nsylvain@chromium.org2009-10-022-34/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27912 0039d316-1c4b-4281-b951-d872f2087c98
* revert this change because protoc.exe crashes during compile and breaks the ↵nsylvain@chromium.org2009-10-022-1/+34
| | | | | | | | | | | | | try servers: Set the LITE runtime optimization flag in sync.proto. This generates c++ code without support for protobuf reflections, and shaves 175000 bytes off of the final release size of syncapi.dll. Review URL: http://codereview.chromium.org/242133 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27910 0039d316-1c4b-4281-b951-d872f2087c98
* Set the LITE runtime optimization flag in sync.proto.nick@chromium.org2009-10-022-34/+1
| | | | | | | | | | | This generates c++ code without support for protobuf reflections, and shaves 175000 bytes off of the final release size of syncapi.dll. BUG=none TEST=tested sync interactively with two clients. Review URL: http://codereview.chromium.org/249034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27818 0039d316-1c4b-4281-b951-d872f2087c98
* Initial commit of sync engine code to browser/sync.nick@chromium.org2009-09-103-0/+398
The code is not built on any platform yet. That will arrive as a subsequent checkin. This is an implementation of the interface exposed earlier through syncapi.h. It is the client side of a sync protocol that lets users sync their browser data (currently, just bookmarks) with their Google Account. Table of contents: browser/sync/ protocol - The protocol definition, and other definitions necessary to connect to the service. syncable/ - defines a data model for syncable objects, and provides a sqlite-based backing store for this model. engine/ - includes the core sync logic, including commiting changes to the server, downloading changes from the server, resolving conflicts, other parts of the sync algorithm. engine/net - parts of the sync engine focused on the business of talking to the server. Some of this is binds a generic "server connection" interface to a concrete implementation provided by Chromium. notifier - the part of the syncer focused on the business of sending and receiving xmpp notifications. Notifications are used instead of polling to achieve very low latency change propagation. util - not necessarily sync specific utility code. Much of this is scaffolding which should either be replaced by, or merged with, the utility code in base/. BUG=none TEST=this code includes its own suite of unit tests. Review URL: http://codereview.chromium.org/194065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25850 0039d316-1c4b-4281-b951-d872f2087c98