ugovaretto / zmq-scratch

Scratchpad for ZeroMQ experiments

zmq-scratch

Scratchpad for ZeroMQ experiments

zmq-scratch's Issues

Add peering example with sync server and robust communication

The current peering example requires all the peer ids to be passed on the command line.
Create version with sync server from which each broker receives notifications when a new broker connects.
No handshaking shall take place:

• brokers register through the sync server
• sync server notifies all brokers of new brokers
• brokers receive the notification, along with the server back-end URI in the main loop (through polling) and connect to it

Add time checking on clients

• replace recv with poll + recv
• time req-reply timing
• in case of timeouts resend the request a number of times and exit after notifying an error through a monitoring channel

test ROUTER-ROUTER envelopes

Cleanup

Review samples and cleanup/add comments and READMEs with detailed explanation in each directory.

zcf - handle exceptions

Implement error callback to cal when exceptions happen in separate thread.

Rename *_messages to *_frames or _message

Consider renaming the multi-part message handling functions to reflect the actual behavior: one message sent as a sequence of frames (sub-messages).

Use iterators in send_messages

Consider using iterators instead of vector reference in send_messages, this allows to send only part of the message if needed, e.g. strip REQ envelope.

Better handling of size reporting (peer brokers, ZGuide ch. 3)

• add a peer --> size map to record available peer capacity, use std::greater as the comparison function to have the peer ordered by greater capacity
• check predicted cloud availability by summing all the sizes in the map
• forward messages to peer with greater predicted capacity i.e. the one at std::map::begin