| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The client and frontends track these separately,
there is no need for hard synchronization.
|
| |
|
| |
|
|
|
|
| |
And more or less finalize out the protocol for this use case.
|
|
|
|
| |
Rather than on redisplay, these get cleared on reconnect.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Future-proofing the protocol.
|
| |
|
|
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.
|