Home/ Questions/Q 6248023
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T12:58:53+00:00

I need to implement a simple message bus: One process only thus no need

  • 0

I need to implement a simple message bus:

  • One process only thus no need do D-Bus.
  • Publish/subscribe to typed events (Could even be QObjects)

I was thinking of using QSignalMapper to tag the “named events”, then re-emitting from a slot or connecting the publishers signal to the subscriber’s signal…

Any suggestions thoughts? Or should I go for the relatively simple design pattern?

PS: AFAICS for D-Bus on windows you need to install “3rd party” software to get it going with Qt.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Why don’t you just use one dedicated QObject subclass as a message bus? There you define all signals hat might be exchanged over the message bus and you provide corresponding notify methods that emit these signals. Now every component that wants to receive “messages” can connect to the signals of interest.

    If you want a more generic method use the same approach as before. However, the (singleton) QObject subclass now only has a “message(QByteArray)” signal and a “sendMessage(QByteArray)” public method which emits this signal. You might want to declare the send message method as being a slot, too, just in case you want to connect another signal to the send method.

    I use these approaches myself and they work perfecty fine. Even different threads can communicate with each other using this mechanism without any problems. If you use the QByteArray approach you will get something similar to DBus. You serialize and deserialize your messages and automatically make sure all message receivers get their own copy of messages with all the benefits you get if you do parallel calculations.

    • 0