commit | 37bcee297e94fa5b06af6c4efbeb4804d236fe11 | [log] [tgz] |
---|---|---|
author | Jixiang Jin <jixiang.jjx@alibaba-inc.com> | Tue Nov 05 10:57:54 2024 +0800 |
committer | GitHub <noreply@github.com> | Tue Nov 05 10:57:54 2024 +0800 |
tree | d8f0256c6c6c0f0c3b40af36cf3686e9811e0afb | |
parent | 70eb1effd4b415678fc7214cedd3a289b0f926b9 [diff] | |
parent | d7b37144502a4d35471994fe32018cae6914a4cc [diff] |
Merge pull request #86 from qianye1001/qianye-main [ISSUE #85] Add MESSAGE_BODY_EMPTY Code.
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.