Thales Macedo Garitezi 19f3b030f9 chore: preparing to run common tests / eunit with mix hai 1 ano
..
include 46877e979b chore: update copyright-year %!s(int64=2) %!d(string=hai) anos
src 80d724c504 feat(authn): add connection expire based on authn data hai 1 ano
test 80d724c504 feat(authn): add connection expire based on authn data hai 1 ano
.gitignore 0a62d6c556 refactor(gw): rename all gateway application name %!s(int64=2) %!d(string=hai) anos
README.md 0a62d6c556 refactor(gw): rename all gateway application name %!s(int64=2) %!d(string=hai) anos
mix.exs 19f3b030f9 chore: preparing to run common tests / eunit with mix hai 1 ano
rebar.config 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` %!s(int64=2) %!d(string=hai) anos

README.md

emqx_stomp

The Stomp Gateway is based on the Stomp v1.2 and is compatible with the Stomp v1.0 and v1.1 specification.

Quick Start

In EMQX 5.0, Stomp gateway can be configured and enabled through the Dashboard.

It can also be enabled via the HTTP API or emqx.conf, e.g. In emqx.conf:

gateway.stomp {

  mountpoint = "stomp/"

  listeners.tcp.default {
    bind = 61613
    acceptors = 16
    max_connections = 1024000
    max_conn_rate = 1000
  }
}

Note: Configuring the gateway via emqx.conf requires changes on a per-node basis, but configuring it via Dashboard or the HTTP API will take effect across the cluster.

More documentations: Stomp Gateway