From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35993)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XwS4E-00053n-KT
	for qemu-devel@nongnu.org; Thu, 04 Dec 2014 03:47:23 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XwS49-0001mO-Mr
	for qemu-devel@nongnu.org; Thu, 04 Dec 2014 03:47:18 -0500
Received: from mx1.redhat.com ([209.132.183.28]:34910)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1XwS49-0001mE-F4
	for qemu-devel@nongnu.org; Thu, 04 Dec 2014 03:47:13 -0500
Message-ID: <1417682821.14168.128.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Thu, 04 Dec 2014 09:47:01 +0100
In-Reply-To: <547FC7C8.6050304@huawei.com>
References: <1417589746-12176-1-git-send-email-arei.gonglei@huawei.com>
	<20141203093807.GA10160@redhat.com> <547EDD01.7050608@huawei.com>
	<1417608638.14168.49.camel@nilsson.home.kraxel.org>
	<547FC7C8.6050304@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard
 layout dynamically
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gonglei <arei.gonglei@huawei.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>, "lcapitulino@redhat.com" <lcapitulino@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "Huangpeng (Peter)" <peter.huangpeng@huawei.com>

  Hi,

> Hum.. Now, I encountered this situation that the common clienteles just use
> tightvnc client, but want to change keymap dynamically. As you say,
> the only way address this scenario is doing it on the server side. So,
> do you think this patch series make sense and consider to accept it
> in upstream? Thanks!

The alternatives are:

 * Try figure why they are using tightvnc.  Do they simply don't know
   there are other vnc clients such as remote-viewer with much better
   keyboard support?  Did they try other clients and want stick to
   tightvnc nevertheless?  If so, what are the reasons?

 * Try add raw scancode extension support to tightvnc (or the
   http://tigervnc.org/ fork).

I see server-side keymap switching as last ressort if all other
approaches failed, simply because the manual keymap configuration needed
on the server side is error-prone and a pretty bad user experience.

cheers,
  Gerd