[Spice-devel] [spice-server v2 8/9] Handle SPICE_MSGC_DISCONNECTING message in RedChannelClient

[Victor Toso]

From: Frediano Ziglio <fziglio at redhat.com>

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 at redhat.com>
---

Rebased to apply cleanly.

 server/inputs-channel.c | 2 --
 server/main-channel.c   | 2 --
 2 files changed, 4 deletions(-)

diff --git a/server/inputs-channel.c b/server/inputs-channel.c
index 15256ba4..51e25969 100644
--- a/server/inputs-channel.c
+++ b/server/inputs-channel.c
@@ -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);
     }
diff --git a/server/main-channel.c b/server/main-channel.c
index 34f54768..a1ffe1d0 100644
--- a/server/main-channel.c
+++ b/server/main-channel.c
@@ -213,8 +213,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;
     case SPICE_MSGC_MAIN_MIGRATE_END:
         main_channel_client_handle_migrate_end(mcc);
         break;
-- 
2.15.1