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

Figure out join() and Drop behavior for DownloadHandle #65

Open
1 of 2 tasks
graebm opened this issue Oct 17, 2024 · 0 comments
Open
1 of 2 tasks

Figure out join() and Drop behavior for DownloadHandle #65

graebm opened this issue Oct 17, 2024 · 0 comments
Assignees

Comments

@graebm
Copy link
Contributor

graebm commented Oct 17, 2024

Currently, DownloadHandle has a join() function, but neither cp.rs or the benchmark runner bother to call it. It was added because UploadHandle has a join(), and we thought the APIs should be similar.

But DownloadHandle::join() cancels the download, while UploadHandle::join() waits for the upload to successfully complete, and has a separate UploadHandle::abort() function. Should we rename DownloadHandle::join() to DownloadHandle::abort()?

Also, what's the Drop behavior for DownloadHandle? We should probably ensure its spawned tasks get cancelled ASAP. Likewise for UploadHandle/UploadObjectsHandle/DownloadObjectsHandle

  • Drop and cancel for UploadHandle/UploadObjectsHandle (PR)
  • Drop and cancel for DownloadHandle/DownloadObjectsHandle
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants