Allow apps receiving a push import to set the ContentStore
Bug #1430075 reported by
Robert Schroll
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| content-hub (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Apps receiving a pull import (one they initiated) can set the ContentStore to have the content delivered to a permanent location. However, apps receiving a push import (initiated from without) cannot, and thus always receive content in the volatile ~/.cache directory. If they wish to save it permanently or be able to modify it, they must move it themselves.
Since apps will likely try to share code between the two import paths, I suspect this will cause most apps to ignore the ContentStore and handle file management manually in both cases. We should allow the ContentStore to be set on push imports as well, so that receivers can always make use of it.
| Changed in content-hub: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: convergence |
Revision history for this message
| Ken VanDine (ken-vandine) wrote | #1 |
| tags: | removed: convergence |
| Changed in content-hub: | |
| importance: | Wishlist → Medium |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| affects: | content-hub → content-hub (Ubuntu) |
| Changed in content-hub (Ubuntu): | |
| assignee: | Ken VanDine (ken-vandine) → nobody |
To post a comment you must log in.
On the receiving end, they should be able to change the ContentTranfers