On 06.01.2011, at 23:57, Aaron J. Seigo wrote: > On Thursday, January 6, 2011, Aaron J. Seigo wrote: >> On Thursday, January 6, 2011, Frank Karlitschek wrote: >>> I´m not sure a batch update call is really needed because this call would >>> have a very low cache hit rate on the server compared with atomic checks >>> for single plasmoids. >>> >>> But a batch check call could be added to the next version of the spec of >>> course if it makes sense. >> >> yes, it's the check call that would benefit from being batched, since it >> determines if any ations need to be taken, and updates will be infrequent >> relative to checks for available updates. > > that was pretty easy. the list command in synchrotron now supports (the non- > standard) createdsince and updatedsince optional parameters which restricts > listings as one would expect. both take a seconds-since-the-epoch timestamp.
Hmm. This parameter is not in the current spec and is not in attica or GHNS supported at the moment and makes it incompatible with clients like the MeeGo Installer an other servers like Maemo garage or others. It also problematic if the user only wants to update a subset of the available updates The current update system works via the version field where the client compares the current installed version with the available version and offers a possible upgrade to the users. It´s always possible to extend this functionality in the next version of the spec if you want but this should be discussed on the ocs list and we need a consensus between all the parties. I think it is important that all the available clients and servers stay compatible. Cheers Frank -- Frank Karlitschek karlitsc...@kde.org _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
