Changed the client to read only a single line worth of response.
This mirrors how the server works, and will be necessary to tell apart further messages. Events will arrive at one per line.
Added Request::EventStream that replies with Response::Handled and then proceeds to write one Event per line as they occur.
Events will be designed in such a way that the initial burst will synchronize the current state to the client, then subsequent events will modify that state in a consistent way. E.g. the initial burst of events will create all current outputs and workspaces.
Compositor-side, event stream clients have a buffer of events for sending. If this buffer runs too large (the client hanged and isn't reading), this client will be dropped. This is kinda similar to what Wayland itself does.
The events are all subject to change until this PR is merged. Currently only the WindowFocused is actually implemented, and I'm planning to change its type too.
Some basic scaffolding for an event stream IPC.
Changed the client to read only a single line worth of response.
This mirrors how the server works, and will be necessary to tell apart further messages. Events will arrive at one per line.
Request::EventStreamthat replies withResponse::Handledand then proceeds to write oneEventper line as they occur.The events are all subject to change until this PR is merged. Currently only the WindowFocused is actually implemented, and I'm planning to change its type too.