https://bugs.gpodder.org/show_bug.cgi?id=1082
Summary: Storing arbitrary Settings
Product: gpodder.net
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: feature request
Priority: low
Component: Advanced API (Server-side)
AssignedTo: [email protected]
ReportedBy: [email protected]
gPodder.net should be able to store and synchronize arbitrary settings
(key-value pairs).
Settings can be attached to either
* account
* device
* podcast
* episode
This can be used by the clients to synchronize configuration settings via
gpodder.net. API endpoints for retrieving, adding and removing settings have to
be added.
API Draft
=========
PUT
/api/2/settings/<username>/(account|device|podcast|episode).json?podcast=<url>&episode=<url>&device=<id>
{"add":
{"setting1": "value1",
{"setting2": "value2"}
"delete": ["setting3", "setting4"]
}
GET
/api/2/settings/<username>/(account|device|podcast|episode).json?setting=<setting>&podcast=<url>&episode=<url>&device=<id>
{"setting1": "value1", "setting2": "value2"}
Example: Paused Subscriptions (#1050)
=====================================
To store the information that a subscription to a podcast has been paused, a
client could
PUT /api/2/settings/user1/podcast.json?podcast=http://podcast.com/feed.xml
{"add": [
{"feed_update_enabled": false}
]
}
another client could then retrieve the setting by
GET /api/2/settings/user1/podcast.json?podcast=http://podcast.com/feed.xml
{"feed_update_enabled": false}
--
Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs
