Upload
summary
Android client implements a persistent upload manager for Odnoklassniki that splits each upload into atomic subtasks stored in a file-backed key space using hierarchical task IDs, so work survives process death and restarts. Images are transcoded client-side, large files upload in 2 MB chunks with parallelism and resume checks against backend, local retries use exponential backoff and server byte-count queries, and network IO uses selector-based nonblocking IO to drive many sockets from one thread while reporting progress into a shared state map for UI.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:13Standard approach problems
- 7:26Ideal upload approach
- 10:44Faster content loading
- 17:55Atomic task architecture
- 23:04Failure recovery
- 25:15Parallel upload technologies
- 27:30User notifications
- 31:22Summary and benefits
- 31:59Q&A
related talks
01h 13mChallenges of developing a client for cloud storage on iOS
23mUser Initiated Data Transfer Jobs
42mAndroid Application Architecture
28mPractical WorkManager
26mBehind the Curtains How Photos TM Work
33mThe making of an Android library: Download Manager v2
32mAndroid @ Dropbox
34mFile API: Client-Side File Handling and Uploading to the Server