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.

Sign up for GitHub

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

Jump to bottom

[Feature] Save interrupted downloads in persistent storage #12

Open
KaustubhPatange opened this issue Aug 16, 2020 · 2 comments
Open

[Feature] Save interrupted downloads in persistent storage #12

KaustubhPatange opened this issue Aug 16, 2020 · 2 comments
Labels
enhancement New feature or request unexpected behaviour Feature working but has unexpected paradigms

Comments

@KaustubhPatange
Copy link
Owner

Is your feature request related to a problem?

No

Describe the solution you'd like:

When a movie is downloading and the user stops the application, it should be saved to persistent storage which can be recovered later when "Download Queue" is opened.

Describe alternatives you've considered:

None
@KaustubhPatange KaustubhPatange added the enhancement New feature or request label Aug 16, 2020
@KaustubhPatange
Copy link
Owner Author

Implementation is possible. Stopping app from recent do call onDestroy() in DownloadService, data can be saved here. Remember to optimize your task to a max 300 ms (which is the maximum time you should spend in onDestroy() otherwise choreographer will get delayed to remove UI from the buffer queue).

@KaustubhPatange KaustubhPatange added the unexpected behaviour Feature working but has unexpected paradigms label Aug 16, 2020
@KaustubhPatange
Copy link
Owner Author

Follows unexpected paradigms due to service lifecycle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request unexpected behaviour Feature working but has unexpected paradigms
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KaustubhPatange