summaryrefslogtreecommitdiffstats
path: root/chrome/browser/sync/syncable
Commit message (Collapse)AuthorAgeFilesLines
* Replace Read/Write lock with a plain old chrome lock.chron@chromium.org2009-10-022-259/+66
| | | | | | | | BUG=19895 Review URL: http://codereview.chromium.org/246056 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27811 0039d316-1c4b-4281-b951-d872f2087c98
* Fix compiling of sync on linux.zork@chromium.org2009-09-224-29/+32
| | | | | | Review URL: http://codereview.chromium.org/211019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26835 0039d316-1c4b-4281-b951-d872f2087c98
* Build the sync unit tests:nick@chromium.org2009-09-161-21/+0
| | | | | | | | | | | | | | | | | | | - Remove old main(argc, argv) from syncable_unittest. - Since the old notifier target had only one unittest, merge it with the syncer tests. - Remove listener_unittest.cc entirely. - Don't compile natserver_main.cc, which has another main() - Use a test main from the test_support_unit library. This has the downside of pulling in a lot of deps we don't need, but it gives us a run_all_unittests.cc. - Fix a few compile errors in test code. TEST=unit tests pass BUG=none Review URL: http://codereview.chromium.org/205021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26358 0039d316-1c4b-4281-b951-d872f2087c98
* Build sync engine as part of the browser build.nick@chromium.org2009-09-154-22/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | As before, syncapi is built as a dynamic library, and only on windows. The difference is that it's built from source, rather than being pulled in as a binary. Changes to sync engine code: * Use OS_WIN instead of OS_WINDOWS (requires build_config.h). * Rename platform-specific files to match the chrome convention. This allows them to be excluded by rules that already exist in chrome.gyp. The convention is either a /win/ directory, or an _win.cc at the end of the file. Other valid platforms are _mac, _linux, and _posix Changes to DEPS: * On Windows, pull in pthreads-win32. Changes to chrome.gyp: * Add new library targets for sync, notifier, sync_proto, and syncapi. Review URL: http://codereview.chromium.org/193103 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26295 0039d316-1c4b-4281-b951-d872f2087c98
* Made some style fixes in the remaining code under chrom/browser/sync and ↵idana@chromium.org2009-09-1410-79/+79
| | | | | | | | under chrome/test/sync. Review URL: http://codereview.chromium.org/203043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26126 0039d316-1c4b-4281-b951-d872f2087c98
* Fix compiler warnings in chrome\browser\sync.nick@chromium.org2009-09-112-2/+2
| | | | | | | | | | | | | Warnings are treated as errors in the Chrome build. Most of these are just forcing the implicit conversion to maintain the previous behavior. TEST=sync unit tests BUG=none Review URL: http://codereview.chromium.org/193085 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26020 0039d316-1c4b-4281-b951-d872f2087c98
* Initial commit of sync engine code to browser/sync.nick@chromium.org2009-09-1017-0/+6493
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