minamanda wrote: > > 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 noticed this over 3 years ago, and raised an issue (https://github.com/nikclayton/android-squeezer/issues/201). I'm not sure why you use such as small pageSize, as this makes "Loading..." appear when scrolling lists. With MaterialSkin, a Javascript app, I request up to 25k at a time - but use a virtual-scroller so that only those shown on the screen are part of the document. If a JavaScript app can load that many and be responsive, a pure Java app should be able to handle even more. So, if you asked for 25k (basically all) items then only draw the visible items this would resolve your issue - and my original reported issue. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. ------------------------------------------------------------------------ cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=112972 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
