From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Support multiple VNC clients
Date: Sun, 15 Feb 2009 11:35:00 +0000 [thread overview]
Message-ID: <20090215113500.GD4795@redhat.com> (raw)
In-Reply-To: <4995CECB.1070401@moose.net>
On Fri, Feb 13, 2009 at 02:49:31PM -0500, Brian Kress wrote:
> Attached is a patch that allows qemu to support multiple vnc clients.
> Each client can have their own
> VNC encodings and VNC state.
>
> General idea:
>
> Change structure associated with a display from VncState to a new
> structure VncDisplay.
> Remove client specific fields from VncDisplay.
> Remove display specific fields from VncState.
> Maintain a linked list of VncStates per VncDisplay structure, update as
> necessary.
> When updates/resizes/copies come in from the hardware, dispatch to all
> clients.
>
>
> Patch is against current SVN (6618)
> Any ideas/suggestions/comments/flames appreciated.
Perhaps also add a -vnc command line flag to let us control policy for
multiple clients interactions ? eg some policies I think of
- Single client, new clients dropped
- Single client, original client dropped
- Many clients, first full access, others view only
- Many clients, all full access
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-02-15 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 19:49 [Qemu-devel] [PATCH] Support multiple VNC clients Brian Kress
2009-02-14 10:07 ` malc
2009-02-14 22:07 ` Anthony Liguori
2009-02-15 1:13 ` Brian Kress
2009-02-16 14:59 ` Anthony Liguori
2009-02-15 11:35 ` Daniel P. Berrange [this message]
2009-02-15 21:47 ` Itamar Heim
2009-02-15 22:21 ` Brian Kress
2009-02-16 0:59 ` Anthony Liguori
2009-02-16 11:32 ` 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=20090215113500.GD4795@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.