From 9cbb6a5fec1d0a9e7b614bde7a4e7d9f21c641e8 Mon Sep 17 00:00:00 2001 From: Ferdinand Schober Date: Mon, 13 Feb 2023 19:17:48 +0100 Subject: [PATCH] Update README.md --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b443f02..e94856e 100644 --- a/README.md +++ b/README.md @@ -79,9 +79,11 @@ cargo run ## Protocol considerations 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. +Each event is sent as one single datagram, currently without any acknowledgement to guarantee 0% packet loss. +This means, any packet that is lost results in a discarded mouse / key event, which is ignored for now. + **UDP** also has the additional benefit 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. +Any client can just go offline and it will simply start working again as soon as it comes back online. Additionally a tcp server is hosted for data that needs to be sent reliably (e.g. the keymap from the server or clipboard contents in the future) can be requested via a tcp connection.