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

StartUploads endpoint Or expiry of stale Uploads entries. #69

Open
crspybits opened this issue May 9, 2018 · 1 comment
Open

StartUploads endpoint Or expiry of stale Uploads entries. #69

crspybits opened this issue May 9, 2018 · 1 comment

Comments

@crspybits
Copy link
Owner

crspybits commented May 9, 2018

It seems like the process for uploading should start with a StartUploads endpoint call. My thought for this is to reset any cruft entries in the Uploads table for this client. For example, suppose that a client had to restart uploads because of a master version change. (Note that these should actually be replaced or the upload just ignored). Or suppose that a client crashed, was deleted and re-installed midway through some uploads.

Another way to deal with this might be to expire entries in the Uploads table after they've been there for a period of time.

Another way would be to have a client delete their own stale entries from Uploads.

@crspybits
Copy link
Owner Author

I'm attaching an example of an image that was stranded in the Shared Images Google Drive -- Haven't yet looked but I'm guessing it has an entry in the Upload table.
1865eb03-ce6e-400c-8aee-8a9a64303b7e f6f4c079-58fd-4bcf-a157-6d8ef00876bb 0

@crspybits crspybits changed the title StartUploads endpoint Or expiry of Uploads entries. StartUploads endpoint Or expiry of stale Uploads entries. Jul 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant