mirror of
https://gitlab.uni-freiburg.de/opensourcevdi/spice-protocol
synced 2026-08-12 18:20:20 +00:00
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.
This commit is contained in:
parent
911dac9d60
commit
f188fb7a89
17
spice.proto
17
spice.proto
@ -1309,6 +1309,22 @@ client:
|
||||
channel UsbredirChannel : SpicevmcChannel {
|
||||
};
|
||||
|
||||
channel PortChannel : SpicevmcChannel {
|
||||
client:
|
||||
message {
|
||||
uint8 event;
|
||||
} event = 201;
|
||||
server:
|
||||
message {
|
||||
uint32 name_size;
|
||||
uint8 *name[name_size] @zero_terminated @marshall @nonnull;
|
||||
uint8 opened;
|
||||
} init = 201;
|
||||
message {
|
||||
uint8 event;
|
||||
} event;
|
||||
};
|
||||
|
||||
protocol Spice {
|
||||
MainChannel main = 1;
|
||||
DisplayChannel display;
|
||||
@ -1319,4 +1335,5 @@ protocol Spice {
|
||||
TunnelChannel tunnel;
|
||||
SmartcardChannel smartcard;
|
||||
UsbredirChannel usbredir;
|
||||
PortChannel port;
|
||||
};
|
||||
|
||||
Loading…
Reference in New Issue
Block a user