googleapis / googleapis/google-api-java-client
Resume uploads on different executions
- 主要語言
- Java
- 星號
- 1.5k
- 分支
- 772
- 平均合併
- 1 小時 44 分鐘
- 30 天內合併 PR
- 1
描述
If I execute a resumable upload for a file, kill the process and then start it again, **there is no way to get the "upload_id"** for the first file in order to continue with the upload in a new process. This can be tested with the `DriveSample` class on GitHub samples.
The class `MediaHttpUploader` creates and maintains a `currentRequest` (`uploadType=resumable&upload_id=...`) during one execution of `resumableUpload(GenericUrl)`. However, there is no way to obtain and maintain that information for future processes.
My intention is to upload backup files in the background. If the user closes my application, I should be able to continue with the upload when the user starts the application again.
Original post: [Issue 4131](https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=4131).
Similar question [here](http://stackoverflow.com/questions/25288849/resumable-uploads-google-drive-sdk-for-android-or-java).
貢獻指南
研究方向
從 DriveSample 類別和 MediaHttpUploader 開始,接著追蹤包含 upload_id 的 resumableUpload(GenericUrl) 及其 currentRequest。確定如何取得上傳識別碼並在程序之間維持它;完成的定義是後續執行可以繼續中斷的上傳。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- api
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100