Skip to content
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

Implement an HTTP remote sync mechanism #189

Closed
indyjo opened this issue Aug 31, 2019 · 0 comments
Closed

Implement an HTTP remote sync mechanism #189

indyjo opened this issue Aug 31, 2019 · 0 comments
Labels
cafs This issue involves BitWrk's storage back-end, CAFS, which has its own repository client This issue involves the BitWrk client software enhancement

Comments

@indyjo
Copy link
Owner

indyjo commented Aug 31, 2019

The new mechanism should support the following use cases:

  • Syncing a file where the sender acts as the HTTP server while the receiver is an HTTP client
  • Syncing a file which the sender is still receiving at the time of the transmission
@indyjo indyjo added cafs This issue involves BitWrk's storage back-end, CAFS, which has its own repository enhancement labels Aug 31, 2019
@indyjo indyjo added this to the BitWrk 0.6.5 milestone Aug 31, 2019
@indyjo indyjo closed this as completed Aug 31, 2019
@indyjo indyjo reopened this Aug 31, 2019
@indyjo indyjo modified the milestones: BitWrk 0.6.5, Client2Client Aug 31, 2019
@indyjo indyjo added the client This issue involves the BitWrk client software label Aug 31, 2019
indyjo added a commit to indyjo/cafs that referenced this issue Sep 2, 2019
indyjo added a commit that referenced this issue Sep 2, 2019
indyjo added a commit that referenced this issue Sep 2, 2019
indyjo added a commit to indyjo/cafs that referenced this issue Sep 7, 2019
indyjo added a commit to indyjo/cafs that referenced this issue Sep 7, 2019
indyjo added a commit that referenced this issue Sep 7, 2019
indyjo added a commit to indyjo/cafs that referenced this issue Sep 7, 2019
indyjo added a commit that referenced this issue Sep 7, 2019
@indyjo indyjo closed this as completed Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cafs This issue involves BitWrk's storage back-end, CAFS, which has its own repository client This issue involves the BitWrk client software enhancement
Projects
None yet
Development

No branches or pull requests

1 participant