sync: Add transaction support #80
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In this mode, the files synced in both the pull and push phases are not put into place until the completion of the phase. Instead, the updated files are staged into a `.bitpocket/staging` folder. Once all the changes are staged, they are moved into place. If the phase is interrupted, perhaps due to network connection quality, then no changes are reflected. This is especially useful when the changes being synchronized include software or data whose changes should be reflected as a whole. This has the caveat of requiring a bit of extra space on the source and destination systems as extra space for all changes is required. However, it has the caveat that, if interrupted, the staged partial file can be used when resuming the transfer. This can greatly speed syncs over shaky network connections.
|
@raphyduck, I included the spirit of your changes; however, in my experimentation, using |
greezybacon
commented
Oct 23, 2018
|
|
||
| ## Perform the transfer as a transaction. If interrupted, no updates are made. | ||
| # Partial file transfers remain to speed up future syncs. This should be | ||
| # combined with the "clean" command to automatically clean up ab |
There was a problem hiding this comment.
oops. Is there going to be a "clean" command?
|
Very nice @greezybacon |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this mode, the files synced in both the pull and push phases are not put into place until the completion of the phase. Instead, the updated files are staged into a
.bitpocket/stagingfolder. Once all the changes are staged, they are moved into place. If the phase is interrupted, perhaps due to network connection quality, then no changes are reflected. This is especially useful when the changes being synchronized include software or data whose changes should be reflected as a whole.This has the caveat of requiring a bit of extra space on the source and destination systems as extra space for all changes is required. However, it has the advantage that, if interrupted, the staged partial files can be used when resuming the transfer. This can greatly speed syncs over shaky network connections.