Ubuntu
content-hub package

Support "permanent" connections

Bug #1425955 reported by Michał Sawicz
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
content-hub (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

There are some use cases where it would be desirable to create a permanent "connection" between content sources and consumers.

Some that I could think of:
- a directory to put your ebooks in that Beru can look at
- an app syncing your photos online
- contact groups to give apps access to

My proposal is that, when applicable, the user could check a checkbox in the share UI to make a share permanent, and apps could then request data from their permanent shares on startup, or a registered helper could get notified on change.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in content-hub (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Mardegan (mardy) wrote :

For some use cases, it looks like a read-only access should be sufficient (and actually preferable), such as cases #1 and #3.
For the #2 (app syncing your online photos) write access would also be needed.

So, ideally, when granting permanent access to a location, it would be great if the developer can specify whether the access needs to be read only or read-write.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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