Problem: inconsistent naming related to routing ids

Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
This commit is contained in:
sigiesec
2017-09-07 09:29:46 +02:00
parent 1daf83079a
commit e00131dd43
11 changed files with 61 additions and 58 deletions

View File

@@ -85,11 +85,11 @@ namespace zmq
void set_event_sink (i_pipe_events *sink_);
// Pipe endpoint can store an routing ID to be used by its clients.
void set_integral_routing_id (uint32_t routing_id_);
uint32_t get_integral_routing_id ();
void set_server_socket_routing_id (uint32_t routing_id_);
uint32_t get_server_socket_routing_id ();
// Pipe endpoint can store an opaque ID to be used by its clients.
void set_routing_id (const blob_t &identity_);
void set_router_socket_routing_id (const blob_t &identity_);
blob_t get_routing_id ();
blob_t get_credential () const;
@@ -227,10 +227,10 @@ namespace zmq
bool delay;
// Identity of the writer. Used uniquely by the reader side.
blob_t routing_id;
blob_t router_socket_routing_id;
// Identity of the writer. Used uniquely by the reader side.
int integral_routing_id;
int server_socket_routing_id;
// Pipe's credential.
blob_t credential;