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:
Frediano Ziglio 2017-12-02 16:01:24 +00:00
parent 89c5d062d6
commit 60d8389bcd
2 changed files with 0 additions and 4 deletions

View File

@ -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);
}

View File

@ -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);
}