All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Hans de Goede <hdegoede@redhat.com>,
	spice-devel <spice-devel@lists.freedesktop.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Spice-devel] [Qemu-devel] spicevmv chardev,	guest agents and paravirtual mouse
Date: Wed, 12 Jan 2011 13:36:06 -0600	[thread overview]
Message-ID: <4D2E02A6.3060308@codemonkey.ws> (raw)
In-Reply-To: <20110112192834.GB19085@playa.tlv.redhat.com>

On 01/12/2011 01:28 PM, Alon Levy wrote:
>
> Regarding wire protocol this would of course be very wasteful. If it's used
> between the guest and host except for the translation overhead, which is minimal
> I think (except for a copy-paste of a large amount of data - I'm not familiar
> enough with XML-RPC but I guess it has some way to pass binary buffers unmodified?),
> I don't have a particular objection, other then hoping we consider alternatives (there
> are a few).
>
> Regarding one-off protocols in general, I agree it creates code duplication
> and should be avoided. In that respect I prefer mechanisems that produce
> implementations from a declarative description. But I would prefer a binary
> protocol, possibly a convertion of the existing spice protocol to declarative
> form (like Alex did to the core spice protocols, see spice.proto and spice1.proto,
> http://cgit.freedesktop.org/spice/spice/tree/spice.proto
> Of course there are many implementations of this outside of spice, like protocol
> buffers). I also don't think a one-off is necessarily a bad thing.
>    

Yeah, it might be worthwhile to look at protocol buffers.

Regards,

Anthony Liguori

>> Note while on the subject of design, I think that having some sort of
>> capabilities negotiation so that we can provide compatibility between
>> different versions is important.
>>
>> Regards,
>>
>> Hans
>>
>>      

  reply	other threads:[~2011-01-12 19:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 16:12 [Qemu-devel] spicevmv chardev, guest agents and paravirtual mouse Gerd Hoffmann
2011-01-12 17:40 ` Anthony Liguori
2011-01-12 18:59   ` [Spice-devel] " Hans de Goede
2011-01-12 19:28     ` Alon Levy
2011-01-12 19:36       ` Anthony Liguori [this message]
2011-01-12 19:34     ` Anthony Liguori
2011-01-13  9:25       ` Gerd Hoffmann
2011-01-13  9:12     ` Gerd Hoffmann
2011-01-13  8:52   ` Gerd Hoffmann
2011-01-13 10:19 ` [Qemu-devel] Re: [Spice-devel] " Tiziano Müller
2011-01-13 10:54   ` Gerd Hoffmann

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=4D2E02A6.3060308@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=hdegoede@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.