tag | 2de0436fd56ae0f4717948badc29bd092ce7094f | |
---|---|---|
tagger | 凌楚 <yangkun.ayk@alibaba-inc.com> | Thu Oct 13 19:12:01 2022 +0800 |
object | 7ed3e267292ea971064d86acee47a8ef60181121 |
Bump to v2.0.1
commit | 7ed3e267292ea971064d86acee47a8ef60181121 | [log] [tgz] |
---|---|---|
author | Jixiang Jin <jixiang.jjx@alibaba-inc.com> | Mon Oct 10 19:35:28 2022 +0800 |
committer | GitHub <noreply@github.com> | Mon Oct 10 19:35:28 2022 +0800 |
tree | aa2aa4f1508bd10a66e93bf52423876cff354b39 | |
parent | d78d4acfc2d262e427ec301f5e9858a1d3313359 [diff] |
add dlq information to message's systemProperties (#64) * add dlq information to message's systemProperties * do the rename work * do the rename work
RocketMQ APIs use Protocol Buffers version 3 (proto3) as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. Reading these definitions can understand RocketMQ 5.0 models and API behaviors easily.
Currently, Apache RocketMQ only supports these APIs over gRPC, a high-performance binary RPC protocol over HTTP/2. The implementation consists of two parts:
proxy
module that implements this specification in the server-side.