mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #863] Can it support protocol switching, such as switching to UDP? #685
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#685
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daoye on GitHub (Sep 1, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/863
In home(work) LAN, the network usually not bad.
Maby we can use UDP protocol to speed up mouse(keyboard) event sync ?
I feeling... This experience will be better...
@shymega commented on GitHub (Sep 1, 2020):
Potentially. It would break compatiability with older versions of
Barrier however, should they be mixed - bear in mind that.
On this date - Mon, Aug 31, 2020 at 06:55:39PM -0700, daoye wrote:
--
Kind regards,
Dom Rodriguez (shymega)
@daoye commented on GitHub (Sep 2, 2020):
@shymega Thanks answer for me.
If it can be compatible with the old version.
For example, TCP is still used in the old version, but in the new version, TCP and UDP are both support, user can switch to UDP or TCP by configuration, if somebody develop this feature, is it possible to consider incorporating this feature into the repository?
@shymega commented on GitHub (Sep 6, 2020):
What do you mean by the 'old' and 'new' version? Are you referring to Synergy, the original codebase? Or Barrier?
@jjtorroglosa commented on GitHub (Sep 15, 2020):
I was just thinking the same. I was wondering if using UDP would result in a better experience.
It could be an opt-in feature. So, backward compatibility wise, it shouldn't be an issue, as far as I can see. Or is it another reason by which it's not a good idea? 🤔
@shymega commented on GitHub (Sep 15, 2020):
Well, I'm still waiting for a reply from @daoye about their interpretation of the 'old'/'new' version. I still would rather keep any protocol changes for a major semver release to be honest. Until I hear back from @daoye, I have very little idea what the proposal is..
@daoye commented on GitHub (Sep 17, 2020):
@shymega Thanks answer to me.
I means, Is it possible to develop a protocol switching feature, The user can choose to use TCP or UDP in the configuration.
Of course, this feature needs to be backward compatible.
@shymega commented on GitHub (Sep 17, 2020):
Yes, in future versions. It is impossible to make it backwards compatible, if we made it UDP by default.
@p12tic commented on GitHub (Jan 10, 2021):
Knowing a little bit about how networking works, implementing a reliable UDP delivery mechanism that would also be secure (Barrier supports SSL) and at least as fast as TCP would be similar in terms of effort and complexity as writing Barrier from scratch.
If there are latency spikes when using Wifi, I suggest doing some diagnostics on why that happens and try to address the problem. UDP won't help if a large number of packets are being lost or delayed due to retransmissions at the Wifi layer.