TheLanc3/lan-mouse
1
0
Fork 0
mirror of https://github.com/feschber/lan-mouse.git synced 2026-04-04 10:41:29 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Ferdinand Schober
2022-09-20 11:06:33 +02:00
committed by GitHub
parent 7c2d9d3a86
commit ca0cb4c900
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -49,7 +49,15 @@ As mentioned the server will only work on sway compiled from source with the abo
- :white_large_square: Gnome Shell Extension (layer shell is not supported)
## Protocol considerations
Currently UDP is used exclusively for all events sent and / or received.
Currently *all* mouse and keyboard events are sent via **UDP** for performance reasons.
Each event is sent as one single datagram so in case a packet is lost the event will simly be discarded, which is likely not much of a concern.
**UDP** also has the additional bandwith that no reconnection logic is required.
So any client can just go offline and it will simply start working again as soon as it comes back online.
Additionally all server instances (in the future everything will be a server) host a tcp server where critical data, that needs to be send reliably (e.g. the keymap from the server or clipboard contents in the future) can be requested via a tcp connection.
For each request a new connection is established so clients can simply retry if a connection is interrupted.
## Bandwidth considerations
The most bandwidth is taken up by mouse events. A typical office mouse has a polling rate of 125Hz
while gaming mice typically have a much higher polling rate of 1000Hz.
A mouse Event consists of 21 Bytes: