summaryrefslogtreecommitdiffstats
path: root/server/red_channel.h
diff options
context:
space:
mode:
authorAlon Levy <alevy@redhat.com>2010-11-07 13:06:36 +0200
committerAlon Levy <alevy@redhat.com>2011-02-07 19:22:44 +0200
commitc0b7abaa486f081eb67538c7e341f43f7182be75 (patch)
tree57d3b37a48a85a8bf90853591fffb2166bf78267 /server/red_channel.h
parenta30a602654d7760da62cf4b7cefd4a5b5bfe2081 (diff)
downloadspice-c0b7abaa486f081eb67538c7e341f43f7182be75.tar.gz
spice-c0b7abaa486f081eb67538c7e341f43f7182be75.tar.xz
spice-c0b7abaa486f081eb67538c7e341f43f7182be75.zip
server/red_channel: unstatic red_channel_pipe_clear (for red_worker)
Diffstat (limited to 'server/red_channel.h')
-rw-r--r--server/red_channel.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/server/red_channel.h b/server/red_channel.h
index 19f1f67c..5a05b82a 100644
--- a/server/red_channel.h
+++ b/server/red_channel.h
@@ -230,5 +230,9 @@ void red_channel_pipe_add_type(RedChannel *channel, int pipe_item_type);
// should be that they ""try"" a little harder, but if the event system is correct it
// should not make any difference.
void red_channel_push(RedChannel *channel);
+// TODO: again - what is the context exactly? this happens in channel disconnect. but our
+// current red_channel_shutdown also closes the socket - is there a socket to close?
+// are we reading from an fd here? arghh
+void red_channel_pipe_clear(RedChannel *channel);
#endif