Review Request: [GSoC] Amarok integration with gpodder.net (GPodder stuff)

Lucas Lira Gomes x8lucas8x at gmail.com
Mon Oct 17 20:58:56 UTC 2011


Hi Stefan,

we can do this way, but I think it isn't efficient.
We only want to know where we stopped, so there is no need to make more than
one episode action.
Unless something like play history is a to-do for Amarok (Bart should know
^^).

Regards, Lucas Lira Gomes.

On 17 October 2011 17:31, Stefan Kögl <stefan at skoegl.net> wrote:

> Hi,
>
> On 10/16/2011 12:20 AM, Stefan Derkits wrote:
> > It uploads an EpisodeAction::PLAY every minute, which is not correct.
> > Play should only be sent once to the Webservice, when I
> > stop/pause/seek (not sure about seek, @stefankoegl can you clarify?)
> > and not every minute.
>
> The play-actions are intended to record one interval that has been
> played by the user at once.
>
> I'll illustrate this with an example.
>
> * User starts playing from the beginning
>  create action 1 with start 00:00
>
> * User plays to 05:00 then seeks to 10:00
>  set position to 05:00 in actions 1 and send it
>  create action 2 with start 10:00
>
> * User plays to 15:00 and stops playback
>  set position to 15:00 in action 2 and send it
>
> gPodder also skips actions if the time plays (difference between stop
> and start) is below some threshold (maybe 5 sec), but you are free to
> ignore such optimizations or invent your own (if they fit into the
> overall concept).
>
> Repeating the same interval periodically doesn't make much sense. The
> server will not try to merge these actions and they will clutter the
> user's history view.
>
>
> -- Stefan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok-devel/attachments/20111017/4addd176/attachment.html>


More information about the Amarok-devel mailing list