Marc-André Lureau f188fb7a89 Add a "port" channel ... A Spice port channel carry arbitrary data between the Spice client and the Spice server. It may be used to provide additional services on top of a Spice connection. For example, a channel can be associated with the qemu monitor for the client to interact with it, just like any qemu chardev. Or it may be used with various protocols, such as the Spice Controller. A port kind is identified simply by its fqdn, such as org.qemu.monitor, org.spice.spicy.test or org.ovirt.controller... The channel is based on Spicevmc which simply tunnels data between client and server. A few messages have been added: SPICE_MSG_PORT_INIT: Describes the port state and fqdn name, should be sent only once when the client connects. SPICE_MSG_PORT_EVENT: Server port event. SPICE_PORT_EVENT_OPENED and SPICE_PORT_EVENT_CLOSED are typical values when the chardev is opened or closed. SPICE_MSGC_PORT_EVENT: Client port event.		2012-12-05 11:24:05 +01:00
python_modules	python_modules/ptypes.py/EnumBaseType.c_enumname: add missing return to fix broken enums generation	2012-06-14 13:53:46 +03:00
spice1.proto	support seamless migration	2012-08-27 09:06:26 +03:00
spice_codegen.py	codegen: include headers locally	2012-03-21 13:24:17 +01:00
spice.proto	Add a "port" channel	2012-12-05 11:24:05 +01:00