mirror of
https://gitlab.uni-freiburg.de/opensourcevdi/spice
synced 2026-08-07 05:57:20 +00:00
Handle SPICE_MSGC_DISCONNECTING message in RedChannelClient
There's no reason to handle this message in a different way in MainChannel and InputsChannel, the default handling will return true in any case. Signed-off-by: Frediano Ziglio <fziglio@redhat.com> Maybe this check should just be removed?
This commit is contained in:
parent
89c5d062d6
commit
60d8389bcd
@ -404,8 +404,6 @@ static bool inputs_channel_handle_message(RedChannelClient *rcc, uint16_t type,
|
||||
activate_modifiers_watch(inputs_channel);
|
||||
break;
|
||||
}
|
||||
case SPICE_MSGC_DISCONNECTING:
|
||||
break;
|
||||
default:
|
||||
return red_channel_client_handle_message(rcc, type, size, message);
|
||||
}
|
||||
|
||||
@ -216,8 +216,6 @@ static bool main_channel_handle_message(RedChannelClient *rcc, uint16_t type,
|
||||
case SPICE_MSGC_PONG:
|
||||
main_channel_client_handle_pong(mcc, (SpiceMsgPing *)message, size);
|
||||
break;
|
||||
case SPICE_MSGC_DISCONNECTING:
|
||||
break;
|
||||
default:
|
||||
return red_channel_client_handle_message(rcc, type, size, message);
|
||||
}
|
||||
|
||||
Loading…
Reference in New Issue
Block a user