[GSoC] UPnP progress report week 3

[Maximilian Kossick]

I don't think so.

> 2) Update checks and query parameters.
>
> I have been wondering how to watch out for collection modifications
> instead of doing full scans. Although updates aren't very frequent, I
> love Amarok's way of updating local collections with new music I just
> copied, and really want to implement this.
> Since kioslaves lack event loops, it is not possible to have a
> continous monitoring thread. My solution is:

I remember a few thread on kde-devel about running threads in
kioslaves. You could start a special thread in your kioslave to
perform your monitoring.

>  * Just like the slave is to have a HTTP like query parameter based
> API for Search(),
>   it will similarly have certain reserved parameters for notification tasks.
>  * When a stat() is called on the slave with *any* path and a query parameter
>    'checkupdate' set, it will just run the event loop and use KDirNotify to
>    broadcast the updated paths. Right now their is code which does
> this, although
>    it has a limitation of not being able to resolve paths for all
> items in the content
>    directory, but which I will fix soon.
>  * The UpnpCollection periodically calls a stat on the slave ( say
> every 5 seconds? )
>    and scans the relevant directories again. This is just like
> polling used when inotify
>    and friends aren't available on local filesystems.
>
> I would love to hear your thoughts on these.
>
> Regards,
> Nikhil
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>