Problem: duplicated code & inconsistent behaviour between

mechanisms

Solution: uniformly require a ZAP domain to be set to activate ZAP
handling, clarify comment on Stonehouse pattern
This commit is contained in:
sigiesec
2017-09-18 15:24:10 +02:00
parent ee8b8bd29c
commit e546f9296e
10 changed files with 48 additions and 35 deletions

View File

@@ -286,8 +286,10 @@ void zmq::session_base_t::read_activated (pipe_t *pipe_)
if (likely (pipe_ == pipe))
engine->restart_output ();
else
else {
// i.e. pipe_ == zap_pipe
engine->zap_msg_available ();
}
}
void zmq::session_base_t::write_activated (pipe_t *pipe_)