aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/lib
diff options
context:
space:
mode:
authorKeith Packard <keithp@keithp.com>2017-02-10 00:22:03 +0100
committerMike Gabriel <mike.gabriel@das-netzwerkteam.de>2017-03-15 11:09:41 +0100
commit9f000842951f6b5cb40208e9254c50ec56f143e6 (patch)
treeffce4c72749c0b6d8daa132ddf451b6822a963f1 /nx-X11/lib
parent6ac805ab4411d3045c99e3ceefe8495ac95d8e15 (diff)
downloadnx-libs-9f000842951f6b5cb40208e9254c50ec56f143e6.tar.gz
nx-libs-9f000842951f6b5cb40208e9254c50ec56f143e6.tar.bz2
nx-libs-9f000842951f6b5cb40208e9254c50ec56f143e6.zip
os/xdmcp: Just send XDMCP keepalive packets once every three minute
Backported from X.org: commit db1089eafc1c5371fa0030202de588d2e2b4f8e5 Author: Keith Packard <keithp@keithp.com> Date: Mon Sep 21 07:16:17 2015 +0100 os/xdmcp: Just send XDMCP keepalive packets once every three minutes There was a complicated scheme to increase the time between keepalives from 3 minutes up to as much as 24 hours in an attempt to reduce network traffic from idle X terminals. X terminals receiving X traffic, or receiving user input would use the 3 minute value; X terminals without any network traffic would use a longer value. However, this was actually broken -- any activity in the X server, either client requests or user input, would end up resetting the keepalive timeout, so a user mashing on the keyboard would never discover that the XDMCP master had disappeared and have the session terminated, which was precisely the design goal of the XDMCP keepalive mechanism. Instead of attempting to fix this, accept the cost of a pair of XDMCP packets once every three minutes and just perform keepalives regularly. This will also make reworking the block and wakeup handler APIs to eliminate select masks easier. Reviewed-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Keith Packard <keithp@keithp.com> Backported-to-NX-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Diffstat (limited to 'nx-X11/lib')
0 files changed, 0 insertions, 0 deletions