-
Notifications
You must be signed in to change notification settings - Fork 88
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
Completed uploads are kept in the TusURLStore when resuming is enabled #26
Comments
Yes, this is the currently expected behavior. tus-java-client does not remove fingerprints at the moment and it would be the task of the library user to take care of cleaning up the URL storage.
There are situations in which the URLs should be cleaned up after the upload is finished and there are other situations where this should not happen. That's why tus-js-client, for example, has the |
See #27 Squashed commit of the following: commit b664f5b11b406d1ecf9b8fb5e2286de15641cc15 Author: Marius <maerious@gmail.com> Date: Thu Jun 13 12:16:27 2019 +0200 Move line endings back to Unix's LF commit b5807b8 Author: Juan Jose Rodriguez <jj.rodriguez@lks.es> Date: Tue Jun 4 17:16:59 2019 +0200 Change uploadFinished visibility to protected commit ebb5eab Author: Juan Jose Rodriguez <jj.rodriguez@lks.es> Date: Tue May 21 14:41:37 2019 +0200 #26 Add support for removeFingerprintOnSuccess config property
This feature has been implemented in #27 |
remove(String fingerprint)
is never called for TusURLStore after a completed uploadThe upload fingerprints are kept at the TusURLStore, this coul be a problem if a persistent URLStore is used as in the Android client where the PreferencesStore is used with this purpose.
Which is the expected behaviour? Should'nt be removed from the URLStore?
The text was updated successfully, but these errors were encountered: