summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlon Levy <alevy@redhat.com>2010-11-07 13:06:36 +0200
committerAlon Levy <alevy@redhat.com>2010-11-07 13:06:36 +0200
commitb9af099651f5f06c69457f3f4cc8ec4b4140a15e (patch)
tree7fdd8e835d691973e8a62cfdbabf7fbb2b24259b
parent9b676108463c9b72dffc8d8eefbf358492a7bf27 (diff)
downloadspice-b9af099651f5f06c69457f3f4cc8ec4b4140a15e.tar.gz
spice-b9af099651f5f06c69457f3f4cc8ec4b4140a15e.tar.xz
spice-b9af099651f5f06c69457f3f4cc8ec4b4140a15e.zip
server/red_channel: unstatic red_channel_pipe_clear (for red_worker)
-rw-r--r--server/red_channel.c3
-rw-r--r--server/red_channel.h4
2 files changed, 5 insertions, 2 deletions
diff --git a/server/red_channel.c b/server/red_channel.c
index 3b9bb293..d955139c 100644
--- a/server/red_channel.c
+++ b/server/red_channel.c
@@ -30,7 +30,6 @@
#include "red_channel.h"
static PipeItem *red_channel_pipe_get(RedChannel *channel);
-static void red_channel_pipe_clear(RedChannel *channel);
static void red_channel_event(int fd, int event, void *data);
/* return the number of bytes read. -1 in case of error */
@@ -570,7 +569,7 @@ int red_channel_is_connected(RedChannel *channel)
return !!channel->peer;
}
-static void red_channel_pipe_clear(RedChannel *channel)
+void red_channel_pipe_clear(RedChannel *channel)
{
PipeItem *item;
if (channel->send_data.item) {
diff --git a/server/red_channel.h b/server/red_channel.h
index 9078237b..dd85c8f2 100644
--- a/server/red_channel.h
+++ b/server/red_channel.h
@@ -233,5 +233,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