tag | ff56f04dc346755ff335358df05c780ce1d0b1c0 | |
---|---|---|
tagger | 凌楚 <yangkun.ayk@alibaba-inc.com> | Thu Dec 15 10:59:17 2022 +0800 |
object | e83a1bceacbef5be465a459965d8edee59cad0c2 |
Release v2.0.2
commit | e83a1bceacbef5be465a459965d8edee59cad0c2 | [log] [tgz] |
---|---|---|
author | zhouxiang <zhouxiang.zzx@alibaba-inc.com> | Tue Dec 06 20:29:22 2022 +0800 |
committer | Zhouxiang Zhan <zhouxzhan@gmail.com> | Wed Dec 07 15:42:10 2022 +0800 |
tree | aa6c7971a753672fe54fe33765a7fa8e6e4573d9 | |
parent | 8e3aaec565f4f5efd3d6bbd84ba937e346a34911 [diff] |
[ISSUE #65] Add `long_polling_timeout` for ReceiveMessageRequest
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.