2010-10-12, 16:13
Isn't it an idea to compact the return (or build it up compacted in the first place) before sending it?
vs.
Both is 100% correct JavaScript and JSON code.
And I think it could be helpfull to update the startpost of this topic with some extra information like JSON is in but not complete and mention the most asked for missing objects, and tell about the alternatives. Like the "old" httpapi that now doesn't accept POST but only GET, EventClient on port 9777 (eventclient.h). And also mention the RAW JSON tcp port on 9090. Might save a lot of questions asked over and over again.
The RAW tcp port is extremely fast, on my (not very cpu powered) remote it's almost four times faster with small requests (partly because the socket is already connected and can stay open).
And is there anything else available besides these?:
Code:
{
"id" : 1,
"jsonrpc" : "2.0",
"result" : {
"audio" : false,
"picture" : false,
"video" : false
}
}
Code:
{"id":1,"jsonrpc":"2.0","result":{"audio":false,"picture":false,"video":false}}
And I think it could be helpfull to update the startpost of this topic with some extra information like JSON is in but not complete and mention the most asked for missing objects, and tell about the alternatives. Like the "old" httpapi that now doesn't accept POST but only GET, EventClient on port 9777 (eventclient.h). And also mention the RAW JSON tcp port on 9090. Might save a lot of questions asked over and over again.
The RAW tcp port is extremely fast, on my (not very cpu powered) remote it's almost four times faster with small requests (partly because the socket is already connected and can stay open).
And is there anything else available besides these?:
- HTTPAPI (80 http)
- vfs (80 http)
- JSON (80 http)
- JSON (9090 TCP)
- UDP Broadcast (8278 UDP)
- EventServer (9777 UDP)