diff options
| author | Yonit Halperin <yhalperi@redhat.com> | 2013-05-07 11:04:59 -0400 |
|---|---|---|
| committer | Yonit Halperin <yhalperi@redhat.com> | 2013-05-08 09:41:04 -0400 |
| commit | f50827e5274cecbfca8cd5a4995215087d8368fc (patch) | |
| tree | 25e40ad0751e785a5ddce2eda1818ce54f5c1b35 /server | |
| parent | 0a4d29b2e134a6330dd78c5ba46dcc652c4db33b (diff) | |
| download | spice-f50827e5274cecbfca8cd5a4995215087d8368fc.tar.gz spice-f50827e5274cecbfca8cd5a4995215087d8368fc.tar.xz spice-f50827e5274cecbfca8cd5a4995215087d8368fc.zip | |
red_worker: fix incorrect is_low_bandwidth after migrating a low bandwidth connection
rhbz#956345
After a spice session has been migrated, we don't retest the network
(user experience considerations). Instead, we obtain the is_low_bandwidth flag
from the src-server, via the migration data.
Before this patch, if we migrated from server s1 to s2 and then to s3,
and if the connection to s1 was a low bandwidth one, we erroneously
passed is_low_bandwidth=FALSE from s2 to s3.
Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
Diffstat (limited to 'server')
| -rw-r--r-- | server/red_worker.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/server/red_worker.c b/server/red_worker.c index be53c1d2..247f1534 100644 --- a/server/red_worker.c +++ b/server/red_worker.c @@ -10199,6 +10199,9 @@ static int display_channel_handle_migrate_data(RedChannelClient *rcc, uint32_t s } else { spice_critical("restoring global lz dictionary failed"); } + + dcc->common.is_low_bandwidth = migrate_data->low_bandwidth_setting; + if (migrate_data->low_bandwidth_setting) { red_channel_client_ack_set_client_window(rcc, WIDE_CLIENT_ACK_WINDOW); if (dcc->common.worker->jpeg_state == SPICE_WAN_COMPRESSION_AUTO) { |