su chen

We add a key-value map to `MQTTClient` in `MQTTContext`, so that we can share information between filters during whole connection. (It will be stored in MQTTClient, not MQTTContext, so it...

We add `Backend()` to `MQTTContext` which has method `Publish(target string, data []byte, headers map[string]string) error` allow filters to send message to backend server.

New yaml fields for connection management: ```yaml # max allowed connected clients on a single MQTT Proxy maxAllowedConnection: 10000 connectionLimit: rate: 10 # max allowed connection in time period burst:...

Hi @jthann thanks for your issue, here is a naive way to solve this problem. We are open to the discussion of server level filter, but it may a little...

Hi @jthann we do some discuss about this issue, we plan to add a special built-in pipeline called `NopPipeline`. And this pipeline do nothing. So previous naive approach become following:...

Hi @jthann thanks a lot for your reply. Here is my understanding about this issue. For `HTTPServer`, if a request match a rule, then exec corresponding pipeline. If not match,...

# Design `Server` (http, mqtt, tcp) create `context` (http context, mqtt context, tcp context) based on single request, and put `context` into `pipeline` which is a chain of `filters`. Filters...

Hi, thanks a lot for your advice! The `Pipeline` itself supports multiple protocols at same time, but we need to design protocol specific context and filters. For example, `HTTPContext` need...

Hi, thanks a lot for your example! This feature is still work in progress, but when it finished, we will update documents and examples for it. Thanks a lot for...

#352 MQTT Pipeline Develop Guide #352 contain information about MQTT pipeline and filter development. Include example yaml.