From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Qemu vnc color depth
Date: Mon, 11 Feb 2008 15:29:33 +0000 [thread overview]
Message-ID: <20080211152933.GB17784@redhat.com> (raw)
In-Reply-To: <47B06763.2000406@eu.citrix.com>
On Mon, Feb 11, 2008 at 03:18:59PM +0000, Stefano Stabellini wrote:
> Daniel P. Berrange wrote:
> >>1) quietly starting to do the conversion on vnc server (not gaining any
> >>performances here);
> >
> >This should be the default behaviour
> >
> >>2) closing the vnc connection with the client, so the client can
> >>reconnect and choose the new pixel format.
> >
> >This is evil. If we need a way to notify the client of colour depth
> >changes, then we should define an official VNC extension for this
> >that clients can implement. cf the desktop-resize extension
> >
> >So, if the client supports the extension use that to notify, otherwise
> >fallback to doing server-side conversions.
>
> This is a good idea, I just hope it won't take ages to be accepted.
> I'll work on this.
There's not really any formal process for VNC extensions. You pretty
much just post to the vnc mailing list & propose what you want to do
and unless its absolutely insane you should get given a psuedo encoding
number reasonably quickly.
Getting it implement in clients is more fun - but feel free to propose
patches to the gtk-vnc mailing list - we aim to be broad compatability
with as many servers as possible & are particularly interested in stuff
that is useful to virtualization. Also send ideas for the protocol
extension there & we can give feedback on how well it'll work from
the client POV.
> >>By default I am doing 1), however the second choice can be enabled
> >>passing the -vnc-switch-bpp command line option.
> >
> >Don't add more command line options - the existing -vnc flag already
> >has the ability to take multiple flags in the format:
> >
> > -vnc hostname:display,flag,flag,flag,flag
> >
> >eg
> >
> > -vnc localhost:1,passwd,tls
>
> another good suggestion, I'll modify the patch to use this.
Great, thanks.
> >Please send this to qemu-devel - we should not be introducing yet more
> >xen-specific forks to the QEMU code we have - it is a maintainance
> >disaster already with the number of patches we have.
> >
>
> Yeah I know, but sending patches to qemu-devel is like &>/dev/null
Yes it can be - you may not get it mereged quickly, but there are quite a
few people who are knowledgable about the VNC server (who don't read
xen-devel) & might give useful feedback.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-02-11 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 11:20 Qemu vnc color depth Stefano Stabellini
2008-02-11 11:31 ` James Harper
2008-02-11 11:37 ` Stefano Stabellini
2008-02-11 14:54 ` Daniel P. Berrange
2008-02-11 15:18 ` Stefano Stabellini
2008-02-11 15:29 ` Daniel P. Berrange [this message]
2008-02-11 15:47 ` Anthony Liguori
2008-02-12 11:23 ` Stefano Stabellini
2008-02-12 14:56 ` Anthony Liguori
2008-02-12 15:10 ` Stefano Stabellini
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=20080211152933.GB17784@redhat.com \
--to=berrange@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.