diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2013-02-24 15:26:14 +0100 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2013-02-28 14:02:18 +0100 |
| commit | 4fde54a2c63720af4f8560a1d7fdce1f8ad2c6bc (patch) | |
| tree | 98bc9777390f2d4fc3e18f90745e3fda006dd583 /spice | |
| parent | cf9600ad6eea5bdf6bc16e60d9c0c760b0b775bf (diff) | |
| download | spice-protocol-4fde54a2c63720af4f8560a1d7fdce1f8ad2c6bc.tar.gz spice-protocol-4fde54a2c63720af4f8560a1d7fdce1f8ad2c6bc.tar.xz spice-protocol-4fde54a2c63720af4f8560a1d7fdce1f8ad2c6bc.zip | |
vd_agent: Add a VD_AGENT_FILE_XFER_STATUS_SUCCESS result value
Currently the sender of a file xfer assumes success on having send the
last data bytes. But the transfer may still fail on the other side.
This commits adds a VD_AGENT_FILE_XFER_STATUS_SUCCESS result value instead.
Since we have not done an agent release with file-xfer support yet, the client
code can simply assume that it will always get *a* VD_AGENT_FILE_XFER_STATUS_
message for a transfer now. As for the existing spice-gtk release with
file-xfer support, if it talks to an agent sending this message, this will
trigger a g_return_if_fail, which is not really pretty, but has no negative
side-effects other then an error message being logged.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'spice')
| -rw-r--r-- | spice/vd_agent.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/spice/vd_agent.h b/spice/vd_agent.h index b71f7d9..a150a6f 100644 --- a/spice/vd_agent.h +++ b/spice/vd_agent.h @@ -79,6 +79,7 @@ enum { VD_AGENT_FILE_XFER_STATUS_CAN_SEND_DATA, VD_AGENT_FILE_XFER_STATUS_CANCELLED, VD_AGENT_FILE_XFER_STATUS_ERROR, + VD_AGENT_FILE_XFER_STATUS_SUCCESS, }; typedef struct SPICE_ATTR_PACKED VDAgentFileXferStatusMessage { |