2013-06-27 20:47:34 +02:00
|
|
|
/*
|
2015-01-22 10:32:06 +01:00
|
|
|
Copyright (c) 2007-2015 Contributors as noted in the AUTHORS file
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
This file is part of 0MQ.
|
|
|
|
|
|
|
|
0MQ is free software; you can redistribute it and/or modify it under
|
|
|
|
the terms of the GNU Lesser General Public License as published by
|
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
0MQ is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU Lesser General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "stream.hpp"
|
|
|
|
#include "pipe.hpp"
|
|
|
|
#include "wire.hpp"
|
|
|
|
#include "random.hpp"
|
|
|
|
#include "likely.hpp"
|
|
|
|
#include "err.hpp"
|
|
|
|
|
|
|
|
zmq::stream_t::stream_t (class ctx_t *parent_, uint32_t tid_, int sid_) :
|
|
|
|
socket_base_t (parent_, tid_, sid_),
|
|
|
|
prefetched (false),
|
|
|
|
identity_sent (false),
|
|
|
|
current_out (NULL),
|
|
|
|
more_out (false),
|
2014-01-19 09:27:57 +01:00
|
|
|
next_rid (generate_random ())
|
2013-06-27 20:47:34 +02:00
|
|
|
{
|
|
|
|
options.type = ZMQ_STREAM;
|
2015-01-23 15:25:40 +01:00
|
|
|
options.raw_socket = true;
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
prefetched_id.init ();
|
|
|
|
prefetched_msg.init ();
|
|
|
|
}
|
|
|
|
|
|
|
|
zmq::stream_t::~stream_t ()
|
|
|
|
{
|
|
|
|
zmq_assert (outpipes.empty ());
|
|
|
|
prefetched_id.close ();
|
|
|
|
prefetched_msg.close ();
|
|
|
|
}
|
|
|
|
|
2013-08-31 15:53:47 +02:00
|
|
|
void zmq::stream_t::xattach_pipe (pipe_t *pipe_, bool subscribe_to_all_)
|
2013-06-27 20:47:34 +02:00
|
|
|
{
|
2013-08-31 15:53:47 +02:00
|
|
|
// subscribe_to_all_ is unused
|
|
|
|
(void)subscribe_to_all_;
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
zmq_assert (pipe_);
|
|
|
|
|
2013-06-28 09:08:54 +02:00
|
|
|
identify_peer (pipe_);
|
|
|
|
fq.attach (pipe_);
|
2013-06-27 20:47:34 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void zmq::stream_t::xpipe_terminated (pipe_t *pipe_)
|
|
|
|
{
|
2013-06-28 09:08:54 +02:00
|
|
|
outpipes_t::iterator it = outpipes.find (pipe_->get_identity ());
|
|
|
|
zmq_assert (it != outpipes.end ());
|
|
|
|
outpipes.erase (it);
|
|
|
|
fq.pipe_terminated (pipe_);
|
|
|
|
if (pipe_ == current_out)
|
|
|
|
current_out = NULL;
|
2013-06-27 20:47:34 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void zmq::stream_t::xread_activated (pipe_t *pipe_)
|
|
|
|
{
|
2013-06-28 09:08:54 +02:00
|
|
|
fq.activated (pipe_);
|
2013-06-27 20:47:34 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void zmq::stream_t::xwrite_activated (pipe_t *pipe_)
|
|
|
|
{
|
|
|
|
outpipes_t::iterator it;
|
|
|
|
for (it = outpipes.begin (); it != outpipes.end (); ++it)
|
|
|
|
if (it->second.pipe == pipe_)
|
|
|
|
break;
|
|
|
|
|
|
|
|
zmq_assert (it != outpipes.end ());
|
|
|
|
zmq_assert (!it->second.active);
|
|
|
|
it->second.active = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
int zmq::stream_t::xsend (msg_t *msg_)
|
|
|
|
{
|
|
|
|
// If this is the first part of the message it's the ID of the
|
|
|
|
// peer to send the message to.
|
|
|
|
if (!more_out) {
|
|
|
|
zmq_assert (!current_out);
|
|
|
|
|
|
|
|
// If we have malformed message (prefix with no subsequent message)
|
|
|
|
// then just silently ignore it.
|
|
|
|
// TODO: The connections should be killed instead.
|
|
|
|
if (msg_->flags () & msg_t::more) {
|
|
|
|
|
|
|
|
// Find the pipe associated with the identity stored in the prefix.
|
|
|
|
// If there's no such pipe return an error
|
|
|
|
blob_t identity ((unsigned char*) msg_->data (), msg_->size ());
|
|
|
|
outpipes_t::iterator it = outpipes.find (identity);
|
|
|
|
|
|
|
|
if (it != outpipes.end ()) {
|
|
|
|
current_out = it->second.pipe;
|
|
|
|
if (!current_out->check_write ()) {
|
|
|
|
it->second.active = false;
|
|
|
|
current_out = NULL;
|
|
|
|
errno = EAGAIN;
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
errno = EHOSTUNREACH;
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-06-28 11:24:14 +02:00
|
|
|
// Expect one more message frame.
|
|
|
|
more_out = true;
|
|
|
|
|
2013-06-27 20:47:34 +02:00
|
|
|
int rc = msg_->close ();
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
rc = msg_->init ();
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-06-28 09:08:54 +02:00
|
|
|
// Ignore the MORE flag
|
2013-06-27 20:47:34 +02:00
|
|
|
msg_->reset_flags (msg_t::more);
|
|
|
|
|
2013-06-28 11:24:14 +02:00
|
|
|
// This is the last part of the message.
|
|
|
|
more_out = false;
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
// Push the message into the pipe. If there's no out pipe, just drop it.
|
|
|
|
if (current_out) {
|
|
|
|
|
|
|
|
// Close the remote connection if user has asked to do so
|
|
|
|
// by sending zero length message.
|
|
|
|
// Pending messages in the pipe will be dropped (on receiving term- ack)
|
2013-06-28 09:08:54 +02:00
|
|
|
if (msg_->size () == 0) {
|
2013-06-27 20:47:34 +02:00
|
|
|
current_out->terminate (false);
|
|
|
|
int rc = msg_->close ();
|
|
|
|
errno_assert (rc == 0);
|
2013-10-28 21:00:42 +01:00
|
|
|
rc = msg_->init ();
|
|
|
|
errno_assert (rc == 0);
|
2013-06-27 20:47:34 +02:00
|
|
|
current_out = NULL;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
bool ok = current_out->write (msg_);
|
2013-06-28 11:24:14 +02:00
|
|
|
if (likely (ok))
|
2013-06-27 20:47:34 +02:00
|
|
|
current_out->flush ();
|
2013-06-28 11:24:14 +02:00
|
|
|
current_out = NULL;
|
2013-06-27 20:47:34 +02:00
|
|
|
}
|
|
|
|
else {
|
|
|
|
int rc = msg_->close ();
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Detach the message from the data buffer.
|
|
|
|
int rc = msg_->init ();
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2014-01-19 09:27:57 +01:00
|
|
|
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
int zmq::stream_t::xsetsockopt (int option_, const void *optval_,
|
|
|
|
size_t optvallen_)
|
|
|
|
{
|
2015-01-23 15:25:40 +01:00
|
|
|
bool is_int = (optvallen_ == sizeof (int));
|
|
|
|
int value = is_int? *((int *) optval_): 0;
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
switch (option_) {
|
2014-01-19 09:27:57 +01:00
|
|
|
case ZMQ_CONNECT_RID:
|
|
|
|
if (optval_ && optvallen_) {
|
|
|
|
connect_rid.assign ((char*) optval_, optvallen_);
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
break;
|
2015-02-18 19:28:58 +01:00
|
|
|
|
2015-01-23 15:25:40 +01:00
|
|
|
case ZMQ_STREAM_NOTIFY:
|
|
|
|
if (is_int && (value == 0 || value == 1)) {
|
2015-02-11 22:09:25 +01:00
|
|
|
options.raw_notify = (value != 0);
|
2015-01-23 15:25:40 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
errno = EINVAL;
|
|
|
|
return -1;
|
|
|
|
}
|
2014-01-19 09:27:57 +01:00
|
|
|
|
2013-06-27 20:47:34 +02:00
|
|
|
int zmq::stream_t::xrecv (msg_t *msg_)
|
|
|
|
{
|
|
|
|
if (prefetched) {
|
|
|
|
if (!identity_sent) {
|
|
|
|
int rc = msg_->move (prefetched_id);
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
identity_sent = true;
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
int rc = msg_->move (prefetched_msg);
|
|
|
|
errno_assert (rc == 0);
|
|
|
|
prefetched = false;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
pipe_t *pipe = NULL;
|
2013-06-28 11:24:14 +02:00
|
|
|
int rc = fq.recvpipe (&prefetched_msg, &pipe);
|
2013-06-27 20:47:34 +02:00
|
|
|
if (rc != 0)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
zmq_assert (pipe != NULL);
|
2013-06-28 11:24:14 +02:00
|
|
|
zmq_assert ((prefetched_msg.flags () & msg_t::more) == 0);
|
2013-06-27 20:47:34 +02:00
|
|
|
|
2013-06-28 11:24:14 +02:00
|
|
|
// We have received a frame with TCP data.
|
|
|
|
// Rather than sendig this frame, we keep it in prefetched
|
|
|
|
// buffer and send a frame with peer's ID.
|
|
|
|
blob_t identity = pipe->get_identity ();
|
|
|
|
rc = msg_->init_size (identity.size ());
|
|
|
|
errno_assert (rc == 0);
|
2015-02-18 19:28:58 +01:00
|
|
|
|
|
|
|
// forward metadata (if any)
|
|
|
|
metadata_t *metadata = prefetched_msg.metadata();
|
|
|
|
if (metadata)
|
|
|
|
msg_->set_metadata(metadata);
|
|
|
|
|
2013-06-28 11:24:14 +02:00
|
|
|
memcpy (msg_->data (), identity.data (), identity.size ());
|
|
|
|
msg_->set_flags (msg_t::more);
|
2013-06-27 20:47:34 +02:00
|
|
|
|
2013-06-28 11:24:14 +02:00
|
|
|
prefetched = true;
|
|
|
|
identity_sent = true;
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
bool zmq::stream_t::xhas_in ()
|
|
|
|
{
|
|
|
|
// We may already have a message pre-fetched.
|
|
|
|
if (prefetched)
|
|
|
|
return true;
|
|
|
|
|
|
|
|
// Try to read the next message.
|
|
|
|
// The message, if read, is kept in the pre-fetch buffer.
|
|
|
|
pipe_t *pipe = NULL;
|
|
|
|
int rc = fq.recvpipe (&prefetched_msg, &pipe);
|
|
|
|
if (rc != 0)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
zmq_assert (pipe != NULL);
|
2013-06-28 11:24:14 +02:00
|
|
|
zmq_assert ((prefetched_msg.flags () & msg_t::more) == 0);
|
2013-06-27 20:47:34 +02:00
|
|
|
|
|
|
|
blob_t identity = pipe->get_identity ();
|
|
|
|
rc = prefetched_id.init_size (identity.size ());
|
|
|
|
errno_assert (rc == 0);
|
2015-02-19 20:22:32 +01:00
|
|
|
|
|
|
|
// forward metadata (if any)
|
|
|
|
metadata_t *metadata = prefetched_msg.metadata();
|
|
|
|
if (metadata)
|
|
|
|
prefetched_id.set_metadata(metadata);
|
|
|
|
|
2013-06-27 20:47:34 +02:00
|
|
|
memcpy (prefetched_id.data (), identity.data (), identity.size ());
|
|
|
|
prefetched_id.set_flags (msg_t::more);
|
|
|
|
|
|
|
|
prefetched = true;
|
|
|
|
identity_sent = false;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
bool zmq::stream_t::xhas_out ()
|
|
|
|
{
|
2013-06-28 09:08:54 +02:00
|
|
|
// In theory, STREAM socket is always ready for writing. Whether actual
|
2013-06-27 20:47:34 +02:00
|
|
|
// attempt to write succeeds depends on which pipe the message is going
|
|
|
|
// to be routed to.
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2013-06-28 09:08:54 +02:00
|
|
|
void zmq::stream_t::identify_peer (pipe_t *pipe_)
|
2013-06-27 20:47:34 +02:00
|
|
|
{
|
|
|
|
// Always assign identity for raw-socket
|
|
|
|
unsigned char buffer [5];
|
|
|
|
buffer [0] = 0;
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
blob_t identity;
|
2014-01-19 09:27:57 +01:00
|
|
|
if (connect_rid.length ()) {
|
|
|
|
identity = blob_t ((unsigned char*) connect_rid.c_str(),
|
|
|
|
connect_rid.length ());
|
|
|
|
connect_rid.clear ();
|
2014-01-20 02:28:13 +01:00
|
|
|
outpipes_t::iterator it = outpipes.find (identity);
|
2015-02-18 19:28:58 +01:00
|
|
|
if (it != outpipes.end ())
|
2014-01-21 20:43:34 +01:00
|
|
|
zmq_assert(false);
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
}
|
2014-01-18 22:08:06 +01:00
|
|
|
else {
|
2014-01-21 20:43:34 +01:00
|
|
|
put_uint32 (buffer + 1, next_rid++);
|
2014-01-20 00:05:20 +01:00
|
|
|
identity = blob_t (buffer, sizeof buffer);
|
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);
In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
2014-01-17 23:34:39 +01:00
|
|
|
memcpy (options.identity, identity.data (), identity.size ());
|
|
|
|
options.identity_size = identity.size ();
|
|
|
|
}
|
2013-06-27 20:47:34 +02:00
|
|
|
pipe_->set_identity (identity);
|
|
|
|
// Add the record into output pipes lookup table
|
|
|
|
outpipe_t outpipe = {pipe_, true};
|
2013-06-28 09:08:54 +02:00
|
|
|
const bool ok = outpipes.insert (
|
|
|
|
outpipes_t::value_type (identity, outpipe)).second;
|
2013-06-27 20:47:34 +02:00
|
|
|
zmq_assert (ok);
|
|
|
|
}
|