Seems to me I'm a bit over my head here, given my meagre programming skills
I think I'll just start with what I have (telnet subscription + manual invocation of JSON data when necessary), and first have at least a semblance of a working notification system, and see what happens.
The problems, as I can see now, will be parsing the telnet subscription feedback: but, like I said, I can always filter on feedback keywords (e.g. "mixer volume", "newsong", "pause"), and get the rest of the info in JSON format, if neccesary. We'll see how fast (or slow) it works.
It would be nice to have some kind of a direct notification "hook" which lets me know when an event I'm interested in has happened, but I guess the above could work, too - in kind of a "roundabout" way
Regards and thanks,
Denis
I think I'll just start with what I have (telnet subscription + manual invocation of JSON data when necessary), and first have at least a semblance of a working notification system, and see what happens.
The problems, as I can see now, will be parsing the telnet subscription feedback: but, like I said, I can always filter on feedback keywords (e.g. "mixer volume", "newsong", "pause"), and get the rest of the info in JSON format, if neccesary. We'll see how fast (or slow) it works.
It would be nice to have some kind of a direct notification "hook" which lets me know when an event I'm interested in has happened, but I guess the above could work, too - in kind of a "roundabout" way
Regards and thanks,
Denis
Comment