emqx/apps/emqx_exproto
Zaiming Shi f000b6583c fix(tls): Ensure tls config integrity
For default tsl version and ciphers, we try to use otp release number
to determin if we want to use tlsv1.3

For default configs, we try to porivde both tlsv1.3 and
ciphers in config (even for commented out configs)
2021-02-09 22:56:28 +01:00
..
docs test(exproto): refine test cases 2021-01-15 09:47:56 +08:00
etc fix(default-config-tls-ciphers): TLS1.3 exclusive ciphers prepended to TLS1.1+TLS1.2 ciphers 2021-02-05 16:21:28 +13:00
include chore(apps): Sync again all apps 2020-12-07 21:30:21 +01:00
priv feat(exproto): use client streaming APIs for handler 2021-01-15 09:47:56 +08:00
src fix(exproto): fix the bad return type for auth 2021-01-25 09:24:03 +08:00
test fix(tls): Ensure tls config integrity 2021-02-09 22:56:28 +01:00
.gitignore chore(apps): Sync again all apps 2020-12-07 21:30:21 +01:00
README.md test(exproto): refine test cases 2021-01-15 09:47:56 +08:00
rebar.config feat(exproto): use client streaming APIs for handler 2021-01-15 09:47:56 +08:00

README.md

emqx-exproto

The emqx_exproto extremly enhance the extensibility for EMQ X. It allow using an others programming language to replace the protocol handling layer in EMQ X Broker.

Feature

  • Based on gRPC, it brings a very wide range of applicability
  • Allows you to use the return value to extend emqx behavior.

Architecture

EMQ X ExProto Arch

Usage

gRPC service

See: priv/protos/exproto.proto

Example

See: https://github.com/grpc-ecosystem/awesome-grpc