On 11/18/2013 01:03 AM, Marc-André Lureau wrote:
Hey Fedor
On Sun, Nov 17, 2013 at 5:48 PM, Fedor Lyakhov fedor.lyak...@gmail.com
wrote:
Marc,
What does VMC stand for here? Is it related to my idea of virtual
media controller, or just a coincidence?
It's a coincidence ;) Hans should
Marc,
What does VMC stand for here? Is it related to my idea of virtual
media controller, or just a coincidence?
Looks like it is related, as it is a transport API to be used for
anyone wanting to pass arbitrary data through additional Spice channel
- correct?
If so, I suggest renaming this
Hey Fedor
On Sun, Nov 17, 2013 at 5:48 PM, Fedor Lyakhov fedor.lyak...@gmail.com wrote:
Marc,
What does VMC stand for here? Is it related to my idea of virtual
media controller, or just a coincidence?
It's a coincidence ;) Hans should know what it really stands for, it
was introduced with
From: Marc-André Lureau marcandre.lur...@redhat.com
This allows to use conveniently GIOStream APIs without caring about
coroutine and Spice messages details.
---
gtk/Makefile.am | 2 +
gtk/channel-base.c | 48 ++
gtk/channel-port.c | 33 +---
gtk/spice-channel-priv.h
Hi,
One note, I would prefer for the adding of the spice_vmc_write_*
helpers to channel-base.c to be done in a separate commit.
Other then that this looks good, ack.
Regards,
Hans
On 06/05/2013 05:39 PM, Marc-André Lureau wrote:
This allows to use conveniently GIOStream APIs without caring
This allows to use conveniently GIOStream APIs without caring about
coroutine and Spice messages details.
---
gtk/Makefile.am | 2 +
gtk/channel-base.c | 48 ++
gtk/channel-port.c | 33 +---
gtk/spice-channel-priv.h | 8 +
gtk/vmcstream.c | 436
