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 the primary / reference implementation of > the extension. > > The reason I'm suggesting, is that I'm inclined to try adding > this VNC extension to QEMU/KVM's VNC server too - this would > in fact also allow Xen to be rebooted/shutdown/etc without > talking to XenServer.
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. How about using "Xen VM control pseudo-encoding", "Xen VM control client message" and "Xen VM control server message"? Colin ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
