>> I think the API should be updated to reflect the new usage --- not >> that we're changing the API in any way, but we are changing its >> interpertation. I'm willing to take a stab at this, if you like --- >> can you point me to the sources for the API document? This will also >> help us make sure that we understand each other, and may help to find >> any issues we haven't considered. > > The relevant documentation is at > http://wiki.gpodder.org/wiki/Web_Services/API_2#Uploading_episode_actions >
There's something that I actually don't understand about the API: why does episode action *upload* return a timestamp? The client shouldn't be using *this* timestamp for the next retrieve -- the timestamp that should be used as the "since" value for retrieval is that returned by the previous *retrieve* request. I changed the API documentation to reflect my above understanding --- please make sure that what I did is correct, feel free to revert if not! (http://wiki.gpodder.org/w/index.php?title=Web_Services%2FAPI_2&action=historysubmit&diff=724&oldid=699) > >> I also think we should go over the client implementations, just to >> make sure that the changes we propose do not break anything. I'm >> willing to look at mygpoclient and gpodder, but I think it would be >> good if someone more familiar with the code also double-checks. >> (Again, basically I think the clients should be ignoring the >> timestamps of received actions altogether.) > > I think Thomas will be the one who knows the client source well enough > to judge this. > > Thomas, would you mind checking what the implications of the changes > discussed here would be for existing gPodder versions? > Sorry, haven't had time to look into this yet, I still hope to look this over in the next couple of days... Dov _______________________________________________ gpodder-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-devel
