From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Marc <sibson@gmail.com>, qemu-devel <qemu-devel@nongnu.org>,
758881@bugs.debian.org, Gonglei <arei.gonglei@huawei.com>,
Gabriele Giacone <1o5g4r8o@gmail.com>,
Marc Sibson <sibson+vncdotool@gmail.com>
Subject: Re: [Qemu-devel] Bug#758881: [bisected] VNC server can't get all sent chars correctly
Date: Tue, 26 Aug 2014 08:08:48 +0200 [thread overview]
Message-ID: <1409033328.8727.9.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <53FC214A.6070109@msgid.tls.msk.ru>
On Di, 2014-08-26 at 09:55 +0400, Michael Tokarev wrote:
> 26.08.2014 09:40, Gerd Hoffmann wrote:
> > There should be a delay after every character. It can be pretty small.
> > 10ms should be enough (you should set TCP_NODELAY though to make sure
> > the key events are not buffered in the network stack).
>
> Is this delay qemu-specific (or, rather, virtualization-specific, so to say,
> when the target - the VNC server - is working with a hardware being emulated),
> or applies to all VNC servers equally?
Dunno, didn't try. Maybe you can hit it with xvnc too. But I'd expect
that software (xvnc) has larger buffers than (emulated) hardware, so it
doesn't trigger that easily.
cheers,
Gerd
prev parent reply other threads:[~2014-08-26 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 8:56 [Qemu-devel] [bisected] VNC server can't get all sent chars correctly Michael Tokarev
2014-08-25 3:19 ` Gonglei (Arei)
2014-08-25 7:30 ` Markus Armbruster
2014-08-25 7:36 ` Gonglei (Arei)
2014-08-25 9:37 ` Gerd Hoffmann
2014-08-25 10:40 ` [Qemu-devel] Bug#758881: " Gabriele Giacone
2014-08-26 4:11 ` Marc
2014-08-26 5:40 ` Gerd Hoffmann
2014-08-26 5:55 ` Michael Tokarev
2014-08-26 6:08 ` Gerd Hoffmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1409033328.8727.9.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=1o5g4r8o@gmail.com \
--cc=758881@bugs.debian.org \
--cc=arei.gonglei@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=sibson+vncdotool@gmail.com \
--cc=sibson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).