conduit 0.6.0
Modern C++23 header-only event-dispatching / event-transport library
Loading...
Searching...
No Matches
Public Attributes | List of all members
conduit::mqtt::Config Struct Reference

#include <transport.hpp>

Collaboration diagram for conduit::mqtt::Config:
Collaboration graph
[legend]

Public Attributes

std::string url
 
std::string client_id
 
std::optional< std::string > username
 
std::optional< std::string > password
 
std::optional< TlsConfigtls
 
int qos = 1
 
bool clean_session = true
 
std::chrono::seconds keep_alive {60}
 
std::chrono::seconds connect_timeout {10}
 
std::string topic = "conduit/envelope"
 Topic this transport binds to.
 
Format format = Format::Cbor
 Wire format used for both outbound publishes and inbound decoding.
 

Member Data Documentation

◆ clean_session

bool conduit::mqtt::Config::clean_session = true

◆ client_id

std::string conduit::mqtt::Config::client_id

◆ connect_timeout

std::chrono::seconds conduit::mqtt::Config::connect_timeout {10}

◆ format

Format conduit::mqtt::Config::format = Format::Cbor

Wire format used for both outbound publishes and inbound decoding.

◆ keep_alive

std::chrono::seconds conduit::mqtt::Config::keep_alive {60}

◆ password

std::optional<std::string> conduit::mqtt::Config::password

◆ qos

int conduit::mqtt::Config::qos = 1

◆ tls

std::optional<TlsConfig> conduit::mqtt::Config::tls

◆ topic

std::string conduit::mqtt::Config::topic = "conduit/envelope"

Topic this transport binds to.

The transport publishes every envelope it receives onto this topic and subscribes to it at attach time. Required — must be a non-empty single topic; multi-topic routing is done by attaching multiple Transport instances to the bus (one per topic), gated by FilteredTransport if you need event-name filtering.

◆ url

std::string conduit::mqtt::Config::url

◆ username

std::optional<std::string> conduit::mqtt::Config::username

The documentation for this struct was generated from the following file: