From 74d74054934f3255e6bbacac58b7d55df6f9ae7f Mon Sep 17 00:00:00 2001 From: Alon Levy Date: Sun, 7 Nov 2010 13:07:35 +0200 Subject: [PATCH] server/red_channel: add red_channel_receive (for red_worker) --- server/red_channel.c | 5 +++++ server/red_channel.h | 8 ++++++++ 2 files changed, 13 insertions(+) diff --git a/server/red_channel.c b/server/red_channel.c index 6bcf6549..b582cd45 100644 --- a/server/red_channel.c +++ b/server/red_channel.c @@ -143,6 +143,11 @@ static void red_peer_handle_incoming(RedsStreamContext *peer, IncomingHandler *h } } +void red_channel_receive(RedChannel *channel) +{ + red_peer_handle_incoming(channel->peer, &channel->incoming); +} + static void red_peer_handle_outgoing(RedsStreamContext *peer, OutgoingHandler *handler) { int n; diff --git a/server/red_channel.h b/server/red_channel.h index 5a05b82a..68de0841 100644 --- a/server/red_channel.h +++ b/server/red_channel.h @@ -234,5 +234,13 @@ void red_channel_push(RedChannel *channel); // 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); +// Again, used in various places outside of event handler context (or in other event handler +// contexts): +// flush_display_commands/flush_cursor_commands +// display_channel_wait_for_init +// red_wait_outgoing_item +// red_wait_pipe_item_sent +// handle_channel_events - this is the only one that was used before, and was in red_channel.c +void red_channel_receive(RedChannel *channel); #endif