gPodder Bug Tracker – Bug 1030
Add support for "economic" episode action retrieval (per-podcast)
Last modified: 2010-08-23 23:54:08 BST
In order to reduce the amount of actions downloaded, the API Version 2 should have an extended version of "Retrieving episode actions":
In this request, the podcast URL is given, and the server should send back an aggregated list of episode actions, so that the client can mark the episodes with the correct status (e.g. it should know which episodes are new, old and deleted, etc..). For this, only the "newest" status should be sent to the client. (There's no need to send all "delete" actions - the most recent is enough for the client to realize the episode has been deleted. The same is true for play actions with position information, as only the latest one is saved by the official client.)
Client apps that are interested in *all* episode actions can still use the existing API method calls to retrieve all episode actions.
I've added the aggregated parameter to the episode action retrieval.
http://repo.or.cz/w/mygpo.git/commit/25f1ed18666229fa6 (already deployed)
When setting aggregated=true only the latest action for each is sent.
Mass-CLOSING all RESOLVED bugs.