aboutsummaryrefslogtreecommitdiff
path: root/xC-proto
Commit message (Collapse)AuthorAgeFilesLines
* xC/xP: relay and render channel modesPřemysl Eric Janouch2022-09-211-1/+3
|
* xC/xP: relay and render channel topicsPřemysl Eric Janouch2022-09-211-36/+37
|
* xC/xP: show own user's info in frontendsPřemysl Eric Janouch2022-09-201-2/+14
|
* xC/xP: implement M-H in the web frontendPřemysl Eric Janouch2022-09-161-5/+9
|
* xC/xP: send buffer type and server statePřemysl Eric Janouch2022-09-111-2/+38
| | | | Also make PM highlighting behaviour consistent.
* xC/xP: support hiding unimportant messages at allPřemysl Eric Janouch2022-09-101-0/+1
|
* xC/xP: only send buffer stats in the initial syncPřemysl Eric Janouch2022-09-101-2/+4
| | | | | The client and frontends track these separately, there is no need for hard synchronization.
* xC/xP: finalize and implement Event.PINGPřemysl Eric Janouch2022-09-081-8/+14
|
* xC: use the relay protocol's RPC for pingsPřemysl Eric Janouch2022-09-081-0/+2
|
* xC/xP: mark highlights and buffer activityPřemysl Eric Janouch2022-09-081-1/+17
| | | | And more or less finalize out the protocol for this use case.
* xP: implement buffer line leakagePřemysl Eric Janouch2022-09-071-0/+1
| | | | Rather than on redisplay, these get cleared on reconnect.
* xP: implement tab completionPřemysl Eric Janouch2022-09-061-0/+2
| | | | | | | | Currently it only goes for the longest common prefix. Refactor WebSocket handling into an abstraction for our protocol. The Go code generater finally needed fixing.
* xC/xP: pass timestamps with millisecond precisionPřemysl Eric Janouch2022-09-061-1/+1
| | | | Future-proofing the protocol.
* xC/xP: turn the action asterisk into a renditionPřemysl Eric Janouch2022-09-051-0/+1
|
* Start X11 and web frontends for xCPřemysl Eric Janouch2022-09-051-0/+120
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.