diff options
author | Martin Sustrik <sustrik@250bpm.com> | 2011-05-22 17:26:53 +0200 |
---|---|---|
committer | Martin Sustrik <sustrik@250bpm.com> | 2011-05-22 17:26:53 +0200 |
commit | acf0b0e515515e51ad32ba7a2d147ce703579478 (patch) | |
tree | d2032009cf46c23aa0f677c2216914f718ab968a /src/pull.cpp | |
parent | 9e6b39925603f9e64db08c469bd628d7ef9465de (diff) |
Introduces bi-directional pipes
So far, there was a pair of unidirectional pipes between a socket
and a session (or an inproc peer). This resulted in complex
problems with half-closed states and tracking which inpipe
corresponds to which outpipe.
This patch doesn't add any functionality in itself, but is
essential for further work on features like subscription
forwarding.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
Diffstat (limited to 'src/pull.cpp')
-rw-r--r-- | src/pull.cpp | 26 |
1 files changed, 20 insertions, 6 deletions
diff --git a/src/pull.cpp b/src/pull.cpp index b9d4433..66457b8 100644 --- a/src/pull.cpp +++ b/src/pull.cpp @@ -27,19 +27,33 @@ zmq::pull_t::pull_t (class ctx_t *parent_, uint32_t tid_) : fq (this) { options.type = ZMQ_PULL; - options.requires_in = true; - options.requires_out = false; } zmq::pull_t::~pull_t () { } -void zmq::pull_t::xattach_pipes (class reader_t *inpipe_, - class writer_t *outpipe_, const blob_t &peer_identity_) +void zmq::pull_t::xattach_pipe (pipe_t *pipe_, const blob_t &peer_identity_) { - zmq_assert (inpipe_ && !outpipe_); - fq.attach (inpipe_); + zmq_assert (pipe_); + pipe_->set_event_sink (this); + fq.attach (pipe_); +} + +void zmq::pull_t::read_activated (pipe_t *pipe_) +{ + fq.activated (pipe_); +} + +void zmq::pull_t::write_activated (pipe_t *pipe_) +{ + // There are no outbound messages in pull socket. This should never happen. + zmq_assert (false); +} + +void zmq::pull_t::terminated (pipe_t *pipe_) +{ + fq.terminated (pipe_); } void zmq::pull_t::process_term (int linger_) |