summaryrefslogtreecommitdiff
path: root/ui/vnc-tls.c
diff options
context:
space:
mode:
authorPeter Lieven <pl@kamp.de>2014-09-05 22:07:41 +0200
committerGerd Hoffmann <kraxel@redhat.com>2014-09-17 15:14:41 +0200
commit86152436eb06a76e495425c1aa862833576fbc71 (patch)
tree8bed12785c8a67a91c12fd19f43a02ee090a4764 /ui/vnc-tls.c
parente4d50d47a9eb15f42bdd561803a29a4d7c3eb8ec (diff)
downloadqemu-86152436eb06a76e495425c1aa862833576fbc71.zip
ui/vnc: set TCP_NODELAY
we currently have the Nagle algorithm enabled for all outgoing VNC updates. This may delay sensitive updates as mouse movements or typing in the console. As we currently prepare all data in a buffer and then send as much as we can disabling the Nagle algorithm should not cause big trouble. Well established VNC servers like TightVNC set TCP_NODELAY as well. A regular framebuffer update request generates exactly one framebuffer update which should be pushed out as fast as possible. Signed-off-by: Peter Lieven <pl@kamp.de> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'ui/vnc-tls.c')
0 files changed, 0 insertions, 0 deletions