summaryrefslogtreecommitdiffstats
path: root/server/spice-server.syms
diff options
context:
space:
mode:
authorMarc-André Lureau <marcandre.lureau@redhat.com>2012-11-30 13:47:55 +0100
committerMarc-André Lureau <marcandre.lureau@redhat.com>2012-12-05 11:46:28 +0100
commit069270f641b617538c17b64d4bebfd4ccb51c6dc (patch)
treef59ef0ed4e1d672396f8fefa59810a42218baaea /server/spice-server.syms
parent616eee84c11939ebe3a28b6134fe819720426f05 (diff)
downloadspice-069270f641b617538c17b64d4bebfd4ccb51c6dc.tar.gz
spice-069270f641b617538c17b64d4bebfd4ccb51c6dc.tar.xz
spice-069270f641b617538c17b64d4bebfd4ccb51c6dc.zip
server: add "port" channel support
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, with a few additional messages. See the description of the channel protocol in spice-common history.
Diffstat (limited to 'server/spice-server.syms')
-rw-r--r--server/spice-server.syms5
1 files changed, 5 insertions, 0 deletions
diff --git a/server/spice-server.syms b/server/spice-server.syms
index eadfed83..2091fe04 100644
--- a/server/spice-server.syms
+++ b/server/spice-server.syms
@@ -130,3 +130,8 @@ SPICE_SERVER_0.11.4 {
global:
spice_server_set_exit_on_disconnect;
} SPICE_SERVER_0.11.2;
+
+SPICE_SERVER_0.12.2 {
+global:
+ spice_server_port_event;
+} SPICE_SERVER_0.11.4;