The MoaT-Link Server
% start main % start synopsis
MoaT-Link requires a data server for message history, retrieval of non-retained or possibly-non-existent messages, and communication between clients.
% end synopsis
Rationale
Message history
MQTT remembers zero or one message per topic. Sometimes it's important to recover old messages. The MoaT-Link server can record them.
Message retrieval
MQTT is very good at giving you a topic's message as fast as possible, but the only way to discover that a messages doesn't exist is to send another message on a different topic. (Actually, this may not even work on a multi-threaded server.)
That is not always a good idea. Thus you can just ask the server for it.
Inter-Client communication
Every program that uses MoaT-Link should connect to a server and broadcast its location and services. Thus any other MoaT-Link user can connect
Data recovery
If your MQTT cluster crashes, restoring the status from a day-old backup may not be the best strategy. The MoaT-Link server will reload the current state from its log and restore the server's state to just before the crash.
Passive Servers
Normally the MoaT-Link servers cooperate closely and continuously discuss
who of them is responsible for whatever needs doing. To keep a particular
server out of this discussion yet still have it exchange data with its
peers, start it with the -L (“local”) option; equivalently, set
“local_only” in the “server” section of the configuration.
% end main
Metadata
Release files for moat-link-server 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| moat_link_server-0.8.0.tar.gz | 36.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moat_link_server-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.3 kB
Release files / moat_link_server-0.8.0.tar.gz
| Download URL | moat_link_server-0.8.0.tar.gz |
|---|---|
| Size | 36.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94a4b24b1c0235f4602e4df8c3743274f41ff067cda65505e44ca4011201ade5
|
|
BLAKE2b-256 checksum How to use checksums |
c41c6f667159fdcc9ff900b40558701c0afac785541cd573780e937aedc57723
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / moat_link_server-0.8.0-py3-none-any.whl
| Download URL | moat_link_server-0.8.0-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d4d6db6f00340e4237ce448bf629eff767b49efa6deaffb6b7dd54b604701bd
|
|
BLAKE2b-256 checksum How to use checksums |
17ea4b8a16ddf280e36def4f82ab8ca8c76c9d079880c0f4eeac33e7f9976f8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for moat-link-server 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.