qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] ui: add support for remote power control to VNC server
Date: Tue, 15 Dec 2020 09:59:31 +0000	[thread overview]
Message-ID: <20201215095931.GE121272@redhat.com> (raw)
In-Reply-To: <20201214110507.kwz74f4kwfofb7x7@sirius.home.kraxel.org>

On Mon, Dec 14, 2020 at 12:05:07PM +0100, Gerd Hoffmann wrote:
> On Fri, Dec 11, 2020 at 04:08:25PM +0000, Daniel P. Berrangé wrote:
> > The "XVP" (Xen VNC Proxy) extension defines a mechanism for a VNC client
> > to issue power control requests to trigger graceful shutdown, reboot, or
> > hard reset.
> 
> Looks good.  Any other clients are supporting this?

AFAIK, it has only been implmeneted in the Xen VNC Proxy's own Java
client. The extension is documented in rfbproto.rst and is trivial
though, so I've now implemented the corresponding client side in
GTK-VNC too.

> 
> > +            case VNC_XVP_ACTION_REBOOT:
> > +                send_xvp_message(vs, VNC_XVP_CODE_FAIL);
> > +                break;
> 
> > +            default:
> > +                send_xvp_message(vs, VNC_XVP_CODE_FAIL);
> > +                break;
> 
> Minor nit:
> 
> These two are identical, so you can drop the first.
> 
> take care,
>   Gerd
> 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2020-12-15 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 16:08 [PATCH] ui: add support for remote power control to VNC server Daniel P. Berrangé
2020-12-14 11:05 ` Gerd Hoffmann
2020-12-15  9:59   ` Daniel P. Berrangé [this message]

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=20201215095931.GE121272@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@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 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).