Add transfer backend for UbuntuOne

Bug #830684 reported by Jason Gerard DeRose
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Dmedia
Won't Fix
High
Unassigned

Bug Description

So dmedia has a very abstract concept of a "store". A store can be the native dmedia FileStore somewhere on the local file system, or it can be a remote service like S3 or whatever.

Currently S3 (via boto) is the only proper remote store supported (both upload and download). You can see the S3 backend plugin here:

http://bazaar.launchpad.net/~dmedia/dmedia/trunk/view/head:/dmedia/backends/s3.py#L97

The base class may not be generic enough yet, may not have the right abstractions:

http://bazaar.launchpad.net/~dmedia/dmedia/trunk/view/head:/dmedia/transfers.py#L243

So this bug may take some slight changes to the TransferBackend base class.

Also, the UbuntuOne Files API doesn't yet support incremental upload (resumable upload), nor doesn't it support Range requests on the download side (needed for resumable download).

Changed in dmedia:
milestone: 11.09 → 11.10
Changed in dmedia:
milestone: 11.10 → 11.11
Changed in dmedia:
milestone: 11.11 → 11.12
Changed in dmedia:
milestone: 11.12 → 12.02
Changed in dmedia:
milestone: 12.02 → 12.03
Changed in dmedia:
milestone: 12.03 → 12.04
Changed in dmedia:
milestone: 12.04 → 12.06
Changed in dmedia:
milestone: 12.06 → 12.08
Changed in dmedia:
milestone: 12.08 → 12.09
Changed in dmedia:
milestone: 12.09 → 12.10
Changed in dmedia:
milestone: 12.10 → 12.11
Changed in dmedia:
milestone: 12.11 → 12.12
Changed in dmedia:
milestone: 12.12 → 13.04
Changed in dmedia:
milestone: 13.04 → 13.05
Changed in dmedia:
milestone: 13.05 → 13.07
Changed in dmedia:
milestone: 13.07 → 13.09
Changed in dmedia:
milestone: 13.09 → 13.11
Changed in dmedia:
milestone: 13.11 → 14.01
Changed in dmedia:
milestone: 14.01 → 14.03
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

As the future of Ubuntu One (at least the file sync part of it) seems a bit uncertain, I'm going to mark this as "wont fix". We can re-evaluate this in the future, of course.

For the time being, I think it's more important to focus on the native Dmedia file sync.

Changed in dmedia:
milestone: 14.03 → none
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.