summaryrefslogtreecommitdiffstats
path: root/python_modules/codegen.py
diff options
context:
space:
mode:
authorMarc-André Lureau <marcandre.lureau@gmail.com>2012-11-30 01:25:44 +0100
committerMarc-André Lureau <marcandre.lureau@gmail.com>2012-12-05 11:24:05 +0100
commitf188fb7a890867ebe5eace38021b1f3e1daa230d (patch)
treef1a302d593026752f1b32ba40aeb024b1c4b4dc7 /python_modules/codegen.py
parent911dac9d60c2f1c332ec1ab877417b74de2c60e0 (diff)
downloadspice-protocol-f188fb7a890867ebe5eace38021b1f3e1daa230d.tar.gz
spice-protocol-f188fb7a890867ebe5eace38021b1f3e1daa230d.tar.xz
spice-protocol-f188fb7a890867ebe5eace38021b1f3e1daa230d.zip
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.
Diffstat (limited to 'python_modules/codegen.py')
0 files changed, 0 insertions, 0 deletions