mosquitto
sobjectizer
mosquitto | sobjectizer | |
---|---|---|
49 | 15 | |
8,420 | 457 | |
1.7% | 1.5% | |
6.5 | 9.1 | |
4 days ago | about 1 month ago | |
C | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mosquitto
-
SObjectizer Tales - Epilogue
mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;
-
Beginner IoT project: LED Web trigger
References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd http://www.proftpd.org/ accessed on 01/27/2018. Filezilla https://filezilla-project.org/ accessed on 01/27/2018. Fritzing https://fritzing.org/ accessed on 05/25/2022. Appendices:
-
Synchronize 25 ESP8266 to start playback of an audio file at the same time
This is a perfect use case for MQTT, e.g. this library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message.
-
Forward Compatibility for Mosquitto MQTT Broker with Docker Compose v2
While working on a personal project Komponist, I was due to update Mosquitto MQTT Broker due to a CVE and found some interesting changes that will impact me in the future when it comes to configuring the Broker. This post provides a solution to make the Broker compatible with future versions using new and less visited concepts in Docker Compose v2, namely:
-
An AsyncAPI Example: Building Your First Event-driven API
Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server
-
A Modern High-Performance Open Source Message Queuing System
I think he means implementation of MQTT protocol, like https://mosquitto.org/
- virtualisation.oci-containers - how can I move away from DockerHub for my image and move to building my own image from Dockerfile on owners repo?
- 7 Best MQTT Client Tools Worth Trying in 2023
- Smart switch contingency?!
-
Need help using Tasmota with Reed sensors on multiple doors
Could MQTT work for you? You'd need a broker like Mosquitto, and then any of a number of MQTT clients.
sobjectizer
-
SObjectizer Tales - Epilogue
Message Delivery Tracing aims to debug an application built on top of SObjectizer. In essence, it logs the primary stages of the message delivery process, allowing visibility into whether there is a suitable subscriber with the corresponding event handler.
-
SObjectizer Tales - 27. Design ideas
An additional rationale for structuring cooperations in hierarchies is to facilitate the sharing and propagation of dispatchers. A recent update of SObjectizer includes new functionalities that allow access to both agent and cooperation dispatchers. This enhancement was prompted by feedback provided by a user and myself.
-
SObjectizer Tales - 26. Dispatcher selection
If a stop signal arrives, it will be enqueued at the end as a demand for image_producer_callback. This means, it will be processed after the other 6 demands currently in the queue. Maybe this is not an issue but in some cases it might be. At this point, another feature of SObjectizer is to consider: agent priorities. Essentially, this feature allows for the demands to be handled in different orders based on the priorities of agents. In this context, if we assign image_producer_callback a higher priority than others, the “stop signal” would be processed before the rest of the requests.
-
SObjectizer Tales - 23. Mutable messages
The real solution consists in using another slick feature of SObjectizer: mutable messages.
-
SObjectizer Tales - 8. Representing errors
However, this kind of filtering is inefficient and might result in a significant run-time cost. Indeed, every empty cv::Mat follows all the message handling workflow, only to be thrown out. Although we expect that empty images will be sporadic, a more idiomatic approach exists: delivery filters.
-
SObjectizer Tales – 6. Is the stream still in progress?
SObjectizer’s agent states are quite sophisticated and provide some utilities that might be useful for developing a working solution. First of all, image_viewer can be modeled as a two-state agent:
-
SObjectizer Tales - 5. Sending commands
An alternative way is using SObjectizer’s timers.
-
Multiplayer, multithreading, and an actor model in C++
Those who came looking for actor model examples should check out sobjectizer
-
What are some candidate libraries for inter-thread communication like message boxes or event systems?
In sobjectizer the ownership is held by "environment" , while in rotor each thread must held appropriate context, when actor environment is running.
-
Sender and Receiver implementations
May be actor frameworks like caf, sobjectizer or rotor is something, that you are looking for.
What are some alternatives?
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
Aedes - Barebone MQTT broker that can run on any stream server, the node way
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
rotor - Event loop friendly C++ actor micro-framework, supervisable
zigbee2mqtt - Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
hivemq-community-edition - HiveMQ CE is a Java-based open source MQTT broker that fully supports MQTT 3.x and MQTT 5. It is the foundation of the HiveMQ Enterprise Connectivity and Messaging Platform
RxCpp - Reactive Extensions for C++
vernemq - A distributed MQTT message broker based on Erlang/OTP. Built for high quality & Industrial use cases. The VerneMQ mission is active & the project maintained. Thank you for your support!
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport