aboutsummaryrefslogtreecommitdiff
path: root/xP/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* xP: use the binary protocol for incoming eventsPřemysl Eric Janouch2022-09-161-1/+3
| | | | | | | | | | | | | | And batch event messages together as much as possible. JSON has proven itself to be really slow (for example, encoding/json.Marshaler is a slow interface), and browsers have significant overhead per WS message. Commands are still sent as JSON, sending them in binary would be a laborious rewrite without measurable merits. The xP server now only prints debug output when requested, because that was another source of major slowdowns.
* Start X11 and web frontends for xCPřemysl Eric Janouch2022-09-051-0/+14
For this, we needed a wire protocol. After surveying available options, it was decided to implement an XDR-like protocol code generator in portable AWK. It now has two backends, per each of: - xF, the X11 frontend, is in C, and is meant to be the primary user interface in the future. - xP, the web frontend, relies on a protocol proxy written in Go, and is meant for use on-the-go (no pun intended). They are very much work-in-progress proofs of concept right now, and the relay protocol is certain to change.