If the client's channel has SPICE_COMMON_CAP_QOS_QUERY, the server's channel can send SPICE_MSG_QOS_QUERY to the client. In response, the client is expected to send back SPICE_MSG_QOS_ACK immediately after it receives the message following the query, and before handling the message. The server can deduce the network conditions using the ack arrival time.
Signed-off-by: Yonit Halperin <yhalp...@redhat.com> --- spice.proto | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/spice.proto b/spice.proto index 71be9ac..4b622d5 100644 --- a/spice.proto +++ b/spice.proto @@ -135,6 +135,8 @@ channel BaseChannel { Data list; /* the msg body is SpiceSubMessageList */ + Empty qos_query; + client: message { uint32 generation; @@ -155,6 +157,8 @@ channel BaseChannel { uint64 time_stamp; link_err reason; } @ctype(SpiceMsgDisconnect) disconnecting; + + Empty qos_ack; }; struct ChannelId { -- 1.7.7.6 _______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel