From: BALATON Zoltan <balaton@eik.bme.hu>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: vnc clipboard support
Date: Thu, 28 Jan 2021 21:47:06 +0100 (CET) [thread overview]
Message-ID: <f6bc8d6a-9ad1-1d94-ff4a-252f92357338@eik.bme.hu> (raw)
In-Reply-To: <CAJ+F1CJvJM0Vjdz1nU92H+x00+NdbqfoJ9TA--9-BuQ8SNmoFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3265 bytes --]
On Fri, 29 Jan 2021, Marc-André Lureau wrote:
> I also had recently some thoughts about how to implement clipboard sharing
> in a more general way for QEMU.
>
> I admit I like Christophe's suggestion ("it's somebody else problem"), but
> it falls short to me as I don't know of a common open-source remoting
> solution for various operating systems, and I don't see how it could
> integrate well with our UI and remote protocols. Or look at reusing some
> VirtualBox code perhaps?
I also thought about VirtualBox may worth a look at as that supports
clipboard sharing and there's also Synergy
[https://en.wikipedia.org/wiki/Synergy_(software)] that I don't know much
but it's cross platform and may support clipboard sharing. It seems to
have an open source fork called Barrier:
https://github.com/debauchee/barrier
Regards,
BALATON Zoltan
> Some things I keep in mind:
> - the spice protocol had a number of iterations to fix some races. It would
> be great not to repeat the same mistakes, and I don't know if VNC have the
> same flaws or not.
> - the spice agent design isn't great: the system agent proxies messages to
> the active session. It would be nice if the new solution didn't have such a
> middle-man.
> - with wayland, clipboard sharing isn't really possible. Or not in a
> seamless way at least. Today it kinda works with some X11 compatibility
> extensions, but this will eventually go away or change behaviour.
> - the GNOME desktop is working on remoting using RDP, and they are
> implementing a DBus interface for it (
> https://gitlab.gnome.org/jadahl/mutter/-/commits/wip/remote-desktop-clipboard
> )
> - it's not just about clipboard. We would also want to have some kind of
> drag and drop (even if limited to files like Spice atm). We may want some
> windowing integration. We may also want to have access to some desktop
> services: apps, documents etc.. And what's not.
>
> That leads me to think that virtio-serial is not very well suited, as it
> doesn't allow various services / processes to come and go. I see vsock as a
> much better alternative. (I also wonder if it handles control flow any
> better btw)
>
> I think we shoud work on getting the free desktops our best-class support.
> To me, this means we need to speak the lingua franca, which is DBus. The
> great thing is that DBus is also equipped to handle services that come and
> go, handling discovery, introspection etc. Various services are already
> available. As mentioned earlier, that's what the GNOME desktop will offer
> for clipboard sharing. There are good chances other desktops will follow if
> that design works, as it should be easy for them to implement the same
> service. That means good reuse of existing desktop code. Speaking DBus on
> Windows, MacOS or Android isn't an issue. However, vsock support may be a
> bit tricky atm.
>
> Fwiw, DBus doesn't yet officially support vsock connections:
> https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/200. This a minor
> detail, as once you give it a fd for transport, it doesn't really care (I
> also took care of glib!1892 and Rust zbus)
>
> Oh and of course, since this is a new daemon, it would be really a shame
> not to write it in a modern language (hint! ;-).
>
> Hope that helps,
>
>
next prev parent reply other threads:[~2021-01-28 20:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 17:12 vnc clipboard support Gerd Hoffmann
2021-01-28 17:35 ` Daniel P. Berrangé
2021-01-29 7:59 ` Gerd Hoffmann
2021-01-28 17:38 ` Christophe de Dinechin
2021-01-29 8:03 ` Gerd Hoffmann
2021-01-29 10:50 ` Christophe de Dinechin
2021-01-29 11:08 ` Daniel P. Berrangé
2021-01-29 14:19 ` Christophe de Dinechin
2021-01-29 14:32 ` Daniel P. Berrangé
2021-02-01 15:27 ` Christophe de Dinechin
2021-02-01 15:51 ` Daniel P. Berrangé
2021-02-01 16:31 ` Christophe de Dinechin
2021-02-01 16:56 ` Daniel P. Berrangé
2021-02-01 17:28 ` Christophe de Dinechin
2021-02-01 17:40 ` Daniel P. Berrangé
2021-02-01 18:45 ` BALATON Zoltan
2021-02-02 11:31 ` Gerd Hoffmann
2021-02-02 12:31 ` BALATON Zoltan
2021-02-02 12:38 ` Daniel P. Berrangé
2021-02-02 13:35 ` Gerd Hoffmann
2021-02-02 16:36 ` Gerd Hoffmann
2021-02-02 21:00 ` Marc-André Lureau
2021-02-03 9:40 ` Gerd Hoffmann
2021-02-02 11:10 ` Gerd Hoffmann
2021-02-02 11:17 ` Daniel P. Berrangé
2021-02-02 11:44 ` Gerd Hoffmann
2021-01-29 15:04 ` Gerd Hoffmann
2021-02-01 17:07 ` Christophe de Dinechin
2021-01-29 11:49 ` Gerd Hoffmann
2021-01-29 13:28 ` Christophe de Dinechin
2021-01-28 17:57 ` Laszlo Ersek
2021-01-29 8:09 ` Gerd Hoffmann
2021-01-29 10:02 ` Daniel P. Berrangé
2021-01-28 20:18 ` Marc-André Lureau
2021-01-28 20:47 ` BALATON Zoltan [this message]
2021-01-29 7:59 ` Christophe de Dinechin
2021-01-29 8:27 ` Gerd Hoffmann
2021-01-29 8:34 ` Marc-André Lureau
2021-01-29 10:33 ` Gerd Hoffmann
2021-01-29 11:10 ` Daniel P. Berrangé
2021-01-29 11:24 ` Daniel P. Berrangé
2021-01-29 11:58 ` Marc-André Lureau
2021-01-29 12:21 ` Daniel P. Berrangé
2021-01-29 12:02 ` Gerd Hoffmann
2021-01-29 12:10 ` Marc-André Lureau
[not found] <CWLP265MB5209050A121EB63FE07F9BD5A8689@CWLP265MB5209.GBRP265.PROD.OUTLOOK.COM>
2023-04-30 16:20 ` VNC " Philipp Hahn
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=f6bc8d6a-9ad1-1d94-ff4a-252f92357338@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.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 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).