|
|
1 year ago | |
|---|---|---|
| .. | ||
| include | 46877e979b chore: update copyright-year | 2 years ago |
| src | 40036895e4 fix: add handle_frame_error/2 to all gateway implementations | 1 year ago |
| test | 76d4bcd47e fix: ensure all gateways called client.connect hook | 1 year ago |
| .gitignore | 0a62d6c556 refactor(gw): rename all gateway application name | 2 years ago |
| README.md | 0a62d6c556 refactor(gw): rename all gateway application name | 2 years ago |
| mix.exs | 19f3b030f9 chore: preparing to run common tests / eunit with mix | 1 year ago |
| rebar.config | 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` | 2 years ago |
The Stomp Gateway is based on the Stomp v1.2 and is compatible with the Stomp v1.0 and v1.1 specification.
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