April 2020
Intermediate to advanced
412 pages
9h 58m
English
The application we created as part of the Exploring the mechanisms of IPC recipe already contains a number of building blocks we can reuse to implement the pub/sub communication.
The Writer class can act as a publisher and the Reader class as a subscriber. We implemented them to handle the strictly defined data types that will define our messages. The named pipes mechanism we used in the preceding recipe works on a byte level and does not guarantee that messages are delivered automatically.
To overcome this limitation, we will use the POSIX message queue API instead of the named pipes. A name used to identify a message queue that both Reader and Writer will accept in their constructors will be used as a topic: