-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider unifying csync_file_stat_s and csync_vio_file_stat_s #1817
Comments
csync_vio_file_stat_s -> csync_file_stat_s -> TREE_WALK_FILE -> SyncFileItem? |
|
jturcotte
added a commit
that referenced
this issue
Aug 22, 2017
This is the first commit trying to unify csync_file_stat_s, csync_vio_file_stat_s and csync_tree_walk_file_s. Use QByteArray and unique_ptr already since I'm not used to track memory allocations and this will make the transition easier. Issue #1817
jturcotte
added a commit
that referenced
this issue
Aug 22, 2017
Just expose csync_file_stat_t since we don't need an abstraction layer anymore. Also pass the nodes of both trees directly to the visitor function. Issue #1817
jturcotte
added a commit
that referenced
this issue
Aug 23, 2017
Now that they use the same structure, avoid _csync_detect_update having to recreate another instance and transfer everything manually. Any instance created during discovery should now be used all the way up to SyncEngine::treewalkFile. This also makes sure that the path and types are properly set in that object instead of having to pass everything as separate parameters. This gets rid of csync_ftw_flags_e which was now converted from, and to csync_ftw_type_e, already in the csync_file_stat_t. Issue #1817
jturcotte
added a commit
that referenced
this issue
Sep 5, 2017
This is the first commit trying to unify csync_file_stat_s, csync_vio_file_stat_s and csync_tree_walk_file_s. Use QByteArray and unique_ptr already since I'm not used to track memory allocations and this will make the transition easier. Issue #1817
jturcotte
added a commit
that referenced
this issue
Sep 5, 2017
Just expose csync_file_stat_t since we don't need an abstraction layer anymore. Also pass the nodes of both trees directly to the visitor function. Issue #1817
jturcotte
added a commit
that referenced
this issue
Sep 6, 2017
Just expose csync_file_stat_t since we don't need an abstraction layer anymore. Also pass the nodes of both trees directly to the visitor function. Issue #1817
jturcotte
added a commit
that referenced
this issue
Sep 15, 2017
Now that they use the same structure, avoid _csync_detect_update having to recreate another instance and transfer everything manually. Any instance created during discovery should now be used all the way up to SyncEngine::treewalkFile. This also makes sure that the path and types are properly set in that object instead of having to pass everything as separate parameters. This gets rid of csync_ftw_flags_e which was now converted from, and to csync_ftw_type_e, already in the csync_file_stat_t. Issue #1817
jturcotte
added a commit
that referenced
this issue
Sep 18, 2017
Now that they use the same structure, avoid _csync_detect_update having to recreate another instance and transfer everything manually. Any instance created during discovery should now be used all the way up to SyncEngine::treewalkFile. This also makes sure that the path and types are properly set in that object instead of having to pass everything as separate parameters. This gets rid of csync_ftw_flags_e which was now converted from, and to csync_ftw_type_e, already in the csync_file_stat_t. Issue #1817
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even though we mostly got rid of the vio abstraction, this is a layer that is still there.
The conversion is handled in
_csync_detect_update
incsync_update.c
Related to #1813
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2358904-consider-unifying-csync_file_stat_s-and-csync_vio_file_stat_s?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: