Thanks for the reply.
Actually I don't call spotty directly. The request/response is from the
Squeezer app, which implements the CometD protocol.
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.
We have always used that scheme, even while we were using the CLI
protocol. For earlier spotty versions this worked (and still does except
for the search request).
Even with all the data I don't think one can tell whether one is
correct, so here is the same request, but with itemsPerResponse = 200:
Request:
Code:
--------------------
{
"clientId": "f56e5614",
"data": {
"request": [
"00:04:20:2e:3c:31",
[
"spotty",
"items",
"0",
"1",
"search:Genesis",
"useContextMenu:1",
"menu:spotty",
"item_id:0.0",
"cachesearch:1"
]
],
"response": "/f56e5614/slim/request/12"
},
"channel": "/slim/request",
"id": "160"
}
--------------------
Response:
Code:
--------------------
{
"channel": "/80d32417/slim/request/4",
"data": {
"title": "Genesis",
"item_loop": [ ... ],
"offset": 0,
"count": 56,
"base": { ... },
"window": {
"windowStyle": "icon_list"
}
},
"id": "22",
"ext": {
"priority": ""
}
}
--------------------
------------------------------------------------------------------------
minamanda's Profile: http://forums.slimdevices.com/member.php?userid=63054
View this thread: http://forums.slimdevices.com/showthread.php?t=112972
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
