On Fri, 11 Dec 2009 22:03:33 +0300 (MSK) malc <av1...@comtv.ru> wrote:
> On Fri, 11 Dec 2009, Izik Eidus wrote: > > > On Fri, 11 Dec 2009 09:57:48 -0600 > > Anthony Liguori <anth...@codemonkey.ws> wrote: > > > [..snip..] > > > > > Spice desgien is highly diffrence than VNC > > The first thing about spice is that it isnt just a framebuffer > > drawing and not a bitmaps protocol. > > > > Spice protocl support multiple graphics commands, multiple surfaces > > drawings, Spice is desgined to render as less as it can on the > > server and instead to render on the client side much of the work, > > To achive this spice use all kind of techniques such as depth > > viewing tree. > > > > We already have patchs that support offscreen surfaces -> the > > architacture for high end 3d, this make things even more > > complicated. > > > > Spice is a library, it is library for remote display, it handle by > > itself all the connection between the spice client to the host that > > run the guest, it include: > > sound, display, keyboard, usb, network tunneling (for printers) and > > so on... > > > > The patchs that we wanted to push into qemu were what is called VDI > > interfaces, it allow to qemu work with what ever interface it want, > > what so bad about that? > > > > I think we should allow freedom of choice to the users to decide > > what protcol they want to use, Spice and VNC are all diffrent and > > were born to meet diffrent goals. > > > > I would happy to answer more questions if anyone have > > Any particular reason for implementing audio as a driver instead of > a capture? Spice doesnt have paravirtual audio driver, it use the AC97 device. >
