From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gad9H-0004Ro-MX
	for qemu-devel@nongnu.org; Thu, 19 Oct 2006 15:01:47 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gad9E-0004K0-Ga
	for qemu-devel@nongnu.org; Thu, 19 Oct 2006 15:01:45 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gad9E-0004Jf-1y
	for qemu-devel@nongnu.org; Thu, 19 Oct 2006 15:01:44 -0400
Received: from [212.227.126.177] (helo=moutng.kundenserver.de)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gad9D-0004Z1-3J
	for qemu-devel@nongnu.org; Thu, 19 Oct 2006 15:01:43 -0400
Received: from localhost ([127.0.0.1])
	by localhost.localdomain with esmtp (Exim 4.62)
	(envelope-from <weil@mail.berlios.de>) id 1Gad99-000160-Mz
	for qemu-devel@nongnu.org; Thu, 19 Oct 2006 21:01:39 +0200
Message-ID: <4537CB93.9050301@mail.berlios.de>
Date: Thu, 19 Oct 2006 21:01:39 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [RFC] qemu-gui based on wxWidgets
	and	libvncclient
References: <1160670903.5105.3.camel@myubuntu.brain-dump.org>	<453302D1.3040500@cs.utexas.edu>
	<45352FCD.6060300@bellard.org>	<Pine.LNX.4.63.0610181218100.14200@wbgn013.biozentrum.uni-wuerzburg.de>	<453634E4.20109@cs.utexas.edu>
	<4537BE55.4070900@bellard.org>
In-Reply-To: <4537BE55.4070900@bellard.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


>>>
>>> Please, please not _another_ vnc hack! The RFB protocol loses all of
>>> its appeal if everybody has proprietary, incompatible extensions! If
>>> you bother to search Google for prior art, here is a link:
>>>
>>> http://www.ks.uni-freiburg.de/php_arbeitdet.php?id=75
>>>
>>> Yes, it is in German, but it already works. No need to add yet
>>> another obscure extension.
>>
>>
>> My German is not very good, but from what I was able to read, it
>> seems like they are just using VNC to transmit the port information
>> for doing esd forwarding.  Presumably this saved a lot of work
>> because no server side code was needed.
>
> I would prefer a self contained solution using the same TCP connection
> as the rest of the protocol.
>
> Regards,
>
> Fabrice.
>
>
>
Video and audio data have different needs, so two connections
would allow one transfering real-time data (maybe without error
correction) for audio, the other can transfer VNC video data
(no need for high priority real-time, but for error free transmission).

Of course, sometimes a single connection makes things much easier
(for example behind a firewall)...

Regards,

Stefan