![]() ![]() This enables the sync state to be kept offline, even while the MEGA account changes, which is important for the Suspended state mentioned below.Sync decisions are always based on comparisions of Cloud, Local, and Last synced state, rather than applying lists of changes from cloud and local.This fixes the old problem where you can overwrite a file on the local side of your sync with an older version deliberately, but the sync would download the newer one from the cloud and overwrite that.Sync logic is now based on what changed since the last time a file was synced.Additionally we are introducing the long-promised update for exclusions, via the. Consider all the possible OS, filesystem, intentions for initial syncing and ongoing updates, interactions with other changes going on in the filesystem and the MEGA account simultaneously, and so on. The ways in which MEGAsync can be used is vast and we can't test every combination of all factors ourselves. The old sync algorithm and those internal limitations were co-dependent on each other, so it was not possible to update one or the other independently in smaller increments.Īt the same time, we have been paying attention to the various issues reported for MEGAsync, and the updates to the sync algorithm include fixes for most of those problems, and enable fixes for the rest.īecause this is such a big update, we would like to invite keen people to try out the updated version before we release it, and report any situations for which the updated version doesn't work for them, or any bugs that they can find. ![]() We have been updating the sync algorithm in conjunction with overcoming some internal limitations in the MEGA SDK library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |