On 2012 Jul 19, at 11:32, Jens Alfke wrote: > every time you make a change, the entire file will have to be uploaded [by > Dropbox] (and downloaded on the other devices) so this doesn't scale well.
I tested this about a year ago and found otherwise. Drag a large file into your Dropbox. Say that it takes 5 minutes to transfer to your other device. Do the bits/second math with your internet connection speed and verify that the transmission time is about as expected. Now change a few bits in the file. Voila! The other device is updated within seconds. Dropbox apparently transmits only changed blocks. Very nice. What's even better, is that I found it also works that way with a Core Data sqlite store. Changing one record in a large store does not transmit the whole store. > it won't resolve conflicts in the file. So if one database row gets changed > on one device, and another one on another device, Dropbox is just going to go > 'duh' and give you two copies of the file, one with each change. That is correct. Dropbox "syncing" works good for "multi-device" situations, not "multi-user". But that is good enough for most consumer applications. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
