Making trackForUrl asynchronous?

Maximilian Kossick maximilian.kossick at googlemail.com
Thu May 15 17:31:47 CEST 2008


On Thu, May 15, 2008 at 3:20 PM, Mark Kretschmann <kretschmann at kde.org> wrote:
> On 5/15/08, Dan Meltzer <parallelgrapefruit at gmail.com> wrote:
>>  After seeing the way ampache currently handles trackForUrl it seems
>>  like it may make sense to make it asynchronous (or add a similar
>>  asynchronous method such as fetchTrackForUrl.)  This doesn't seem like
>>  it would be too difficult, we could either return MetaProxy's until
>>  the track was fetched or simply not return a track at all and emit a
>>  signal when its fetched.
>>
>>  Thoughts?
>
> Sounds like a good idea to me, especially since startup can become
> really slow with a large number of Ampache tracks in the playlist.

Which is why MetaProxys should be used when loading the playlist.

The idea to make trackForUrl async came up before, but so far I
haven't had a good idea about how to implement it, and I haven't heard
one from anybody else.

Max

> --
> Mark Kretschmann
> Amarok Developer
> www.kde.org - amarok.kde.org
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>


More information about the Amarok-devel mailing list