From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJDVn-0000LA-Ez for qemu-devel@nongnu.org; Fri, 11 Dec 2009 16:58:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJDVh-0000H9-2G for qemu-devel@nongnu.org; Fri, 11 Dec 2009 16:58:54 -0500 Received: from [199.232.76.173] (port=59234 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJDVg-0000H4-Sy for qemu-devel@nongnu.org; Fri, 11 Dec 2009 16:58:48 -0500 Received: from mail-yx0-f188.google.com ([209.85.210.188]:56266) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJDVg-0002kf-GN for qemu-devel@nongnu.org; Fri, 11 Dec 2009 16:58:48 -0500 Received: by yxe26 with SMTP id 26so1294900yxe.4 for ; Fri, 11 Dec 2009 13:58:46 -0800 (PST) Message-ID: <4B22C093.2090806@codemonkey.ws> Date: Fri, 11 Dec 2009 15:58:43 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Spice project is now open References: <1393046876.1549021260539141025.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <4B226BFC.1040606@codemonkey.ws> <20091211204828.464707cf@redhat.com> <4B2297A2.8040102@codemonkey.ws> <20091211212135.645864f9@redhat.com> <4B229DCE.7070500@codemonkey.ws> <20091211213911.0dce90dc@redhat.com> <4B22A2D9.6020602@codemonkey.ws> <20091211223250.129675fc@redhat.com> <4B22B035.3010601@codemonkey.ws> <20091211233158.22e6681f@redhat.com> In-Reply-To: <20091211233158.22e6681f@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Izik Eidus Cc: Yaniv Kamay , qemu-devel@nongnu.org Izik Eidus wrote: > Ok, I guess you think VDI-interfaces are doing much more than they do > in reiality. > > It is just simple interface to Allow Spice / VNC / whatever not have to > de-duplicate code in order to get information from - lets say the > keyboard.... > > Is it really diffrence from any other function callbacks that used for > such purpuse? > Plugin interfaces have been discussed a few times in the past. The concerns have been 1) they will be abused with the introduction of proprietary plugins 2) we would have tremendous difficulty maintaining a stable plugin abi 3) they would create stability issues in qemu because the plugin quality cannot be controlled. For 3, it's a matter of getting a bug report of a crash in qemu with a random plugin module enabled. How do we know whether the crash is really a qemu bug or whether it was an issue in the plugin? This isn't so bad in dynamic languages like Python but it's a real pain in C. Regards, Anthony Liguori > >> Regards, >> >> Anthony Liguori >> >> >> > >