The paging parameters (<start> and <itemsPerResponse>) are set by the client much as squeezeplay etc. does it. Only squeezeplay always does [0, 200] while we initially use [0, 1]. This is done to quickly get the count, so we can set up the UI. Other items are then collected in background in chunks of 20 (i.e. itemsPerResponse = 20). This way we only fetch the on-screen portion of the data.
I haven't fully debugged this. But I don't think this is Spotty specific, as FWICT Spotty would always request the same number of results.
Did you test the performance improvement? I'd expect most of the time to be spent between LMS and the music service. Sure, on a slow connection the amount of data can have an impact, too. But in most cases I'd expect this to be neglectable. All other UIs I know of don't face this problem after all.
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
