data-synchronization

I have an application that also has a web interface, one of the requirements is to be able to work on the application even if there isn't an internet connection available. Is there a need to sync between those databases? Those databases are ought to be pretty big disk space wise. If there is such a need how should it be done? What database should I use? The target OS is windows but the server could run on windows or linux.< Do you mean you need to be able to work via the web application even when offline? Sounds like you need Google Gears or another HTML5 structured storage implementation. If

This question is about using Dropbox to sync an sqlite Core Data store between multiple iOS devices. Consider this arrangement: An app utilizes a Core Data store, call it local.sql , saved in the app's own NSDocumentDirectory The app uses the Dropbox Sync API to observe a certain file in the user's Dropbox, say, user/myapp/synced.sql The app observes NSManagedObjectContextDidSaveNotification , and on every save it copies local.sql to user/myapp/synced.sql , thereby replacing the latter. When the Dropbox API notifies us that synced.sql changed, we do the opposite of part 3 more or less: tear

I have a web application that relies on a MySQL database, for which I am thinking of building an iPhone app. This app would allow users to browse/insert/update/delete data on their account on the web application. The easiest way would be to build the iPhone app simply as an interface for the web app, ie each operation requires to be connected to the web. However, I would like the iPhone app to have its own "offline" version of the database. This would not only allow the user to work offline, but would also provide a better experience, as having everything locally means a faster and more

There is frequently the need to synchronize data from master tables in one database to clone tables in other databases, often on other servers. For example, consider the case where a backend system manages inventory data and that inventory data ultimately must be pushed to one or more databases that are part of a web site application. The source data in the backend system is heavily normalized, with dozens of tables and foreign key constraints. It is a well-designed OLTP RDBMS system. Many of the tables in question contain millions of rows. The need is to push this data out to the other

We're building an API and mobile app on top of a database that has a few hundred thousand records in the main table of interest. Our mobile developer is pushing hard about pre-loading the app with the full table in a local db, then having a service which the phone can sync changes against an updated_at column. While this can definitely increase performance of the app by having it search a local store, I'm worried this will create a lot of load on the server as we acquire more customers. Has anyone else dealt with this? Is it a good idea, bad idea? Can you share some insights and links?

I am working on syncing two business objects between an iPhone and a Web site using an XML-based payload and would love to solicit some ideas for an optimal routine. The nature of this question is fairly generic though and I can see it being applicable to a variety of different systems that need to sync business objects between a web entity and a client (desktop, mobile phone, etc.) The business objects can be edited, deleted, and updated on both sides. Both sides can store the object locally but the sync is only initiated on the iPhone side for disconnected viewing. All objects have an

I'm looking for a javascript library that will let me store data in a client side database and in the back ground automatically sync the database back to the server's database preferable something that supports a variaty of engines in the same way jStore for jQuery does Looking around I can find anything Store.js deal with the client-side storage very well. Note that it supports IE6+ along with other browsers. For the server-side storage you might as well make your own script for that as it should not be difficult. Sam Dutton Since this question was asked, there's been a lot of work done on