From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Ongoing changes to the displaying code
Date: Fri, 09 Jan 2009 19:39:24 -0600 [thread overview]
Message-ID: <4967FC4C.3080201@codemonkey.ws> (raw)
In-Reply-To: <20090110000101.GB1972@shareable.org>
Jamie Lokier wrote:
> The other concern with VNC might be its complexity means you really
> always want to use the existing VNC client library, which may not be a
> desirable dependency for some applications. For this, localhost-VNC
> being both an extension to VNC and a subset of it would be helpful, as
> you wouldn't have to use a full-fledged VNC client library for local
> GUI apps if that isn't wanted.
>
As a protocol, VNC features are almost exclusively client driven. You
can write an extremely simple client with very little code if you just
avoid using advanced features. If all you care about is localhost using
shared memory, this is entirely reasonable.
Admittedly, there's a learning curve simply because there is a lot in
VNC but the vast majority of it is optional.
Regards,
Anthony Liguori
> -- Jamie
>
>
>
next prev parent reply other threads:[~2009-01-10 1:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 1:52 [Qemu-devel] Ongoing changes to the displaying code Daniel Gutson
2009-01-09 2:50 ` Anthony Liguori
2009-01-09 3:04 ` Anthony Liguori
2009-01-09 9:28 ` David Turner
2009-01-09 15:20 ` Anthony Liguori
2009-01-09 16:53 ` David Turner
2009-01-09 17:16 ` Ian Jackson
2009-01-09 17:24 ` Anthony Liguori
2009-01-09 17:42 ` Riku Voipio
2009-01-09 18:59 ` Anthony Liguori
2009-01-10 0:01 ` Jamie Lokier
2009-01-10 1:39 ` Anthony Liguori [this message]
2009-01-12 15:25 ` Ian Jackson
2009-01-15 8:53 ` Mark McLoughlin
2009-01-09 17:26 ` David Turner
2009-01-09 19:02 ` Anthony Liguori
2009-01-12 15:31 ` Ian Jackson
2009-01-11 8:22 ` Avi Kivity
2009-01-12 15:33 ` Ian Jackson
2009-01-12 15:57 ` Avi Kivity
2009-01-09 12:04 ` 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=4967FC4C.3080201@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).