----- Original Message -----
> From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt(a)kohlvanwijngaarden.nl>,
> Sent: Friday, July 27, 2012 12:01:32 PM
> Subject: Re: [Engine-devel] Adding VNC support
> On Jul 26, 2012, at 16:55 , Alon Bar-Lev wrote:
>> On Thu, Jul 26, 2012 at 5:51 PM, Ewoud Kohl van Wijngaarden
>> <ewoud+ovirt(a)kohlvanwijngaarden.nl> wrote:
>>> On Thu, Jul 26, 2012 at 07:36:43AM -0700,
>>> snmishra(a)linux.vnet.ibm.com wrote:
>>>> I am looking at adding VNC support in ovirt. What does the
>>>> think? Ideas, suggestions, comments?
>>> By that I think you mean adding VNC support to the java-based web
>>> interface. In that case +1. I can recommend noVNC, but you do
>>> need a
>>> websockets proxy. I can recommend VNCAuthProxy as a
>>> proxy with a JSON control channel. On the plus side all
>>> dependencies are
>>> in fedora/epel. Downside is no IPv6 support. Maybe you can also
>>> write a
>>> pure java implementation integrate this into the engine itself?
>>> : http://kanaka.github.com/noVNC/
>>> : https://code.osuosl.org/projects/twisted-vncauthproxy/
>> Or launch client program via MIME bindings both for Vnc and
>> Not as neat as "noVnc" but will work in most scenarios, without
>> to maintain the actual console implementation.
> I would think there are many people out there who are not able to use
> current spice client, or not willing to(hate switching from chrome
> to firefox:-)
> Sure they can set up things manually but it would be way more
> convenient to allow a simple external launch of their VNC client of
Exactly what I think.
In time the installation of the client can set up the MIME binding automatically.
that means patching all the vnc clients iiuc, to set mime for multiple