ZIO
Python and C++ interface to ZeroMQ and Zyre
|
#include <client.hpp>
Public Member Functions | |
Client (zio::socket_t &sock, std::string broker_address) | |
~Client () | |
void | send (std::string service, zio::multipart_t &request) |
void | recv (zio::multipart_t &reply) |
The ZIO domo client API class
Applications may use a Client to simplify participating in the GDP client subprotocol. The protocol is exercised through calls to Client::send() and Client::recv().
The application must arrange to use the "clientish" socket corresponding to what is in use by the broker but otherwise, differences related to the socket type are subsequently erased by this class.
Definition at line 22 of file client.hpp.
Client::Client | ( | zio::socket_t & | sock, |
std::string | broker_address | ||
) |
Create a client requesting service. Caller keeps socket eg so to poll it along with others.
Definition at line 7 of file domo_client.cpp.
Client::~Client | ( | ) |
Definition at line 28 of file domo_client.cpp.
void Client::recv | ( | zio::multipart_t & | reply | ) |
Receive a reply from the last request. The reply message holds frames corresponding to "Frames 3+ Reply body" of 7/MDP. If an error occurs the reply is empty.
Definition at line 54 of file domo_client.cpp.
void Client::send | ( | std::string | service, |
zio::multipart_t & | request | ||
) |
Send a request for a service and its associated data. The request message should correspond to "Frames 3+ Request body" of 7/MDP.
Definition at line 44 of file domo_client.cpp.