On Mon, Jun 01, 2009 at 01:09:44PM +0200, Peter Rosin wrote:
Den 2009-06-01 11:37 skrev Pierre Ossman:
On Fri, 29 May 2009 21:41:22 +0100
Colin Dean c.c.d...@durham.ac.uk wrote:
I suggest just stick with xvp, which is what it's been called up to
now. After all, it could be applied to
Hi all,
I think the point Colin is trying to make is that he wants to stick
to xvp as that name has already been exposed, google has indexed it
etc etc. Changing the name this late will only cause confusion.
So, instead of trying to find some (poor) expansion of xvp, we just
leave it at
On Fri, 29 May 2009 07:29:40 +0100
DEAN C.C. c.c.d...@durham.ac.uk wrote:
That sounds like a perfectly good description, Peter.
Pierre: would you be happy if I changed all occurrences of (Xen VNC
Proxy) in my patch to (eXtension for Virtual machine Power options)?
It's a lot more generic,
On Fri, 29 May 2009 07:29:40 +0100
DEAN C.C. c.c.d...@durham.ac.uk wrote:
That sounds like a perfectly good description, Peter.
Pierre: would you be happy if I changed all occurrences of (Xen VNC
Proxy) in my patch to (eXtension for Virtual machine Power options)?
It's a lot more
-rfbproto@lists.sourceforge.net
Subject: Re: [rfbproto] [PATCH] Describe the xvp extension
On Wed, 27 May 2009 10:18:46 +0100
Colin Dean c.c.d...@durham.ac.uk wrote:
It would be really good if QEMU/KVM's VNC server supported this.
Can we agree on some naming, and then I'll submit a new patch
Hi Daniel,
I think perhaps it might be desirable to change the description
to avoid direct reference to Citrix XenServer / XVP in the docs.
Instead say that the XVP extension allows for lifecycle control
of a virtual machine associated with the VNC server. Then refer
to XVP / XenServer as
