However, it does appear likely at the moment that:
- Python will be involved
- WebRTC will be involved (in some cases)
- Browsers will be involved
This leads me to consider WebSockets, which is bi-directional message passing, supported by Browsers, and also now naively by Python and other languages.
Python is in scope due to it being the language of choice on the Pi, and is covered by a number of libraries which claim WebSocket support.
WebRTC is in scope due to the requirement for "Signalling," which is the discovery and transfer of media/network details. This can easily be done over WebSockets, and is seemingly commonly done that way.
Browsers are in scope since any control systems put together would be much nicer with a point-and-click interface, and Browsers are perfect for this.
So, I have deiced to learn how to implement, in Python, some libraries which can act as the middleware between my Pi and the internet (probably a relay of some sort for WebRTC Signalling).
Also any process-to-process communication on the Pi can be done over WebSockets because why not. Keep it all simple and hopefully make the testing easier as well.