This is an automated email from the ASF dual-hosted git repository.
jinrongtong pushed a commit to branch new-official-website
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/new-official-website by this
push:
new 68f4e8b12 fix mqtt docs (#491)
68f4e8b12 is described below
commit 68f4e8b12672b9bc7fe09e9a09511158ab214ac8
Author: pingww <[email protected]>
AuthorDate: Tue Jan 31 10:28:10 2023 +0800
fix mqtt docs (#491)
---
docs/{08-iot => 08-IoT}/33RocketMQMQTTOverview.md | 0
docs/{08-iot => 08-IoT}/34RocketMQMQTTQuickStart.md | Bin
.../08-IoT}/33RocketMQMQTTOverview.md | 8 ++++----
.../{08-iot => 08-IoT}/34RocketMQMQTTQuickStart.md | Bin
.../current/picture/34rocketmq-mqtt/arch.png | Bin 734576 -> 0 bytes
.../current/picture/34rocketmq-mqtt/earch.png | Bin 0 -> 959243 bytes
.../current/picture/34rocketmq-mqtt/eone.png | Bin 0 -> 364336 bytes
.../current/picture/34rocketmq-mqtt/epushpull.png | Bin 0 -> 453878 bytes
.../current/picture/34rocketmq-mqtt/one.png | Bin 184556 -> 0 bytes
.../current/picture/34rocketmq-mqtt/pushpull.png | Bin 463713 -> 0 bytes
.../08-IoT}/33RocketMQMQTTOverview.md | 8 ++++----
.../{08-iot => 08-IoT}/34RocketMQMQTTQuickStart.md | Bin
.../version-5.0/picture/34rocketmq-mqtt/arch.png | Bin 734576 -> 0 bytes
.../version-5.0/picture/34rocketmq-mqtt/earch.png | Bin 0 -> 959243 bytes
.../version-5.0/picture/34rocketmq-mqtt/eone.png | Bin 0 -> 364336 bytes
.../version-5.0/picture/34rocketmq-mqtt/epushpull.png | Bin 0 -> 453878 bytes
.../version-5.0/picture/34rocketmq-mqtt/one.png | Bin 184556 -> 0 bytes
.../version-5.0/picture/34rocketmq-mqtt/pushpull.png | Bin 463713 -> 0 bytes
.../{08-iot => 08-IoT}/33RocketMQMQTTOverview.md | 0
.../{08-iot => 08-IoT}/34RocketMQMQTTQuickStart.md | Bin
20 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/docs/08-iot/33RocketMQMQTTOverview.md
b/docs/08-IoT/33RocketMQMQTTOverview.md
similarity index 100%
rename from docs/08-iot/33RocketMQMQTTOverview.md
rename to docs/08-IoT/33RocketMQMQTTOverview.md
diff --git a/docs/08-iot/34RocketMQMQTTQuickStart.md
b/docs/08-IoT/34RocketMQMQTTQuickStart.md
similarity index 100%
rename from docs/08-iot/34RocketMQMQTTQuickStart.md
rename to docs/08-IoT/34RocketMQMQTTQuickStart.md
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-iot/33RocketMQMQTTOverview.md
b/i18n/en/docusaurus-plugin-content-docs/current/08-IoT/33RocketMQMQTTOverview.md
similarity index 95%
rename from
i18n/en/docusaurus-plugin-content-docs/version-5.0/08-iot/33RocketMQMQTTOverview.md
rename to
i18n/en/docusaurus-plugin-content-docs/current/08-IoT/33RocketMQMQTTOverview.md
index 22b4a0bdc..61a904226 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-iot/33RocketMQMQTTOverview.md
+++
b/i18n/en/docusaurus-plugin-content-docs/current/08-IoT/33RocketMQMQTTOverview.md
@@ -3,7 +3,7 @@ The traditional message queue MQ is mainly used for message
communication betwee
If there is a unified message system (product) to provide multi-scenario
computing (such as stream, event) and multi-scenario (IoT, APP) access, it is
actually very valuable, because messages are also important data. There is only
one system, which can minimize storage costs and effectively avoid the
consistency problems and challenges caused by data synchronization between
different systems.
-
+
Based on this, we introduced the RocketMQ-MQTT extension project to realize
RocketMQ's unified access to the messages of IoT devices and servers, and
provide integrated message storage and intercommunication capabilities.
@@ -16,14 +16,14 @@ The MQTT protocol defines a Pub/Sub communication model,
which is similar to Roc
### Queue Storage Model
-We have designed a topic queue model for multi-dimensional distribution. As
shown in the figure above, messages can come from various access scenarios
(such as MQ/AMQP on the server side and MQTT on the client side), but only one
copy will be written and stored in the commitlog, and then Distribute the queue
index (ConsumerQueue) of multiple demand scenarios. For example, the
server-side scenario (MQ/AMQP) can perform traditional server-side consumption
according to the first-level Topic [...]
+We have designed a topic queue model for multi-dimensional distribution. As
shown in the figure above, messages can come from various access scenarios
(such as MQ/AMQP on the server side and MQTT on the client side), but only one
copy will be written and stored in the commitlog, and then Distribute the queue
index (ConsumerQueue) of multiple demand scenarios. For example, the
server-side scenario (MQ/AMQP) can perform traditional server-side consumption
according to the first-level Topic [...]
Such a queue model can support the access and message sending and receiving of
the server and terminal scenarios at the same time, achieving the goal of
integration.
### Push-Pull Model
-
+
The above figure shows a push-pull model. The P node in the figure is a
protocol gateway or broker plug-in, and the terminal device is connected to the
gateway node through the MQTT protocol. Messages can be sent from a variety of
scenarios (MQ/AMQP/MQTT). After being stored in the Topic queue, there will be
a notify logic module to sense the arrival of the new message in real time, and
then a message event (that is, the topic name of the message) will be
generated. The event is pushed t [...]
## Architecture Overview
-
+
Our goal is to achieve an integrated and self-closed loop based on RocketMQ,
but we don't want Broker to be invaded into more scenario logic. We abstract a
protocol computing layer, which can be a gateway or a broker plug-in. Broker
focuses on solving Queue issues and doing some Queue storage adaptation or
transformation to meet the above computing needs. The protocol computing layer
is responsible for protocol access and must be pluggable and deployed.
\ No newline at end of file
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/08-iot/34RocketMQMQTTQuickStart.md
b/i18n/en/docusaurus-plugin-content-docs/current/08-IoT/34RocketMQMQTTQuickStart.md
similarity index 100%
rename from
i18n/en/docusaurus-plugin-content-docs/current/08-iot/34RocketMQMQTTQuickStart.md
rename to
i18n/en/docusaurus-plugin-content-docs/current/08-IoT/34RocketMQMQTTQuickStart.md
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/arch.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/arch.png
deleted file mode 100644
index 8501d7e35..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/arch.png
and /dev/null differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/earch.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/earch.png
new file mode 100644
index 000000000..1c4f4835e
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/earch.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/eone.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/eone.png
new file mode 100644
index 000000000..4a20341de
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/eone.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/epushpull.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/epushpull.png
new file mode 100644
index 000000000..ee07b4f48
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/epushpull.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/one.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/one.png
deleted file mode 100644
index 79e337833..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/one.png
and /dev/null differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/pushpull.png
b/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/pushpull.png
deleted file mode 100644
index 25e50ea9d..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/current/picture/34rocketmq-mqtt/pushpull.png
and /dev/null differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/08-iot/33RocketMQMQTTOverview.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-IoT/33RocketMQMQTTOverview.md
similarity index 95%
rename from
i18n/en/docusaurus-plugin-content-docs/current/08-iot/33RocketMQMQTTOverview.md
rename to
i18n/en/docusaurus-plugin-content-docs/version-5.0/08-IoT/33RocketMQMQTTOverview.md
index 22b4a0bdc..61a904226 100644
---
a/i18n/en/docusaurus-plugin-content-docs/current/08-iot/33RocketMQMQTTOverview.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-IoT/33RocketMQMQTTOverview.md
@@ -3,7 +3,7 @@ The traditional message queue MQ is mainly used for message
communication betwee
If there is a unified message system (product) to provide multi-scenario
computing (such as stream, event) and multi-scenario (IoT, APP) access, it is
actually very valuable, because messages are also important data. There is only
one system, which can minimize storage costs and effectively avoid the
consistency problems and challenges caused by data synchronization between
different systems.
-
+
Based on this, we introduced the RocketMQ-MQTT extension project to realize
RocketMQ's unified access to the messages of IoT devices and servers, and
provide integrated message storage and intercommunication capabilities.
@@ -16,14 +16,14 @@ The MQTT protocol defines a Pub/Sub communication model,
which is similar to Roc
### Queue Storage Model
-We have designed a topic queue model for multi-dimensional distribution. As
shown in the figure above, messages can come from various access scenarios
(such as MQ/AMQP on the server side and MQTT on the client side), but only one
copy will be written and stored in the commitlog, and then Distribute the queue
index (ConsumerQueue) of multiple demand scenarios. For example, the
server-side scenario (MQ/AMQP) can perform traditional server-side consumption
according to the first-level Topic [...]
+We have designed a topic queue model for multi-dimensional distribution. As
shown in the figure above, messages can come from various access scenarios
(such as MQ/AMQP on the server side and MQTT on the client side), but only one
copy will be written and stored in the commitlog, and then Distribute the queue
index (ConsumerQueue) of multiple demand scenarios. For example, the
server-side scenario (MQ/AMQP) can perform traditional server-side consumption
according to the first-level Topic [...]
Such a queue model can support the access and message sending and receiving of
the server and terminal scenarios at the same time, achieving the goal of
integration.
### Push-Pull Model
-
+
The above figure shows a push-pull model. The P node in the figure is a
protocol gateway or broker plug-in, and the terminal device is connected to the
gateway node through the MQTT protocol. Messages can be sent from a variety of
scenarios (MQ/AMQP/MQTT). After being stored in the Topic queue, there will be
a notify logic module to sense the arrival of the new message in real time, and
then a message event (that is, the topic name of the message) will be
generated. The event is pushed t [...]
## Architecture Overview
-
+
Our goal is to achieve an integrated and self-closed loop based on RocketMQ,
but we don't want Broker to be invaded into more scenario logic. We abstract a
protocol computing layer, which can be a gateway or a broker plug-in. Broker
focuses on solving Queue issues and doing some Queue storage adaptation or
transformation to meet the above computing needs. The protocol computing layer
is responsible for protocol access and must be pluggable and deployed.
\ No newline at end of file
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-iot/34RocketMQMQTTQuickStart.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/08-IoT/34RocketMQMQTTQuickStart.md
similarity index 100%
rename from
i18n/en/docusaurus-plugin-content-docs/version-5.0/08-iot/34RocketMQMQTTQuickStart.md
rename to
i18n/en/docusaurus-plugin-content-docs/version-5.0/08-IoT/34RocketMQMQTTQuickStart.md
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/arch.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/arch.png
deleted file mode 100644
index 8501d7e35..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/arch.png
and /dev/null differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/earch.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/earch.png
new file mode 100644
index 000000000..1c4f4835e
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/earch.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/eone.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/eone.png
new file mode 100644
index 000000000..4a20341de
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/eone.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/epushpull.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/epushpull.png
new file mode 100644
index 000000000..ee07b4f48
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/epushpull.png
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/one.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/one.png
deleted file mode 100644
index 79e337833..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/one.png
and /dev/null differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/pushpull.png
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/pushpull.png
deleted file mode 100644
index 25e50ea9d..000000000
Binary files
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/34rocketmq-mqtt/pushpull.png
and /dev/null differ
diff --git a/versioned_docs/version-5.0/08-iot/33RocketMQMQTTOverview.md
b/versioned_docs/version-5.0/08-IoT/33RocketMQMQTTOverview.md
similarity index 100%
rename from versioned_docs/version-5.0/08-iot/33RocketMQMQTTOverview.md
rename to versioned_docs/version-5.0/08-IoT/33RocketMQMQTTOverview.md
diff --git a/versioned_docs/version-5.0/08-iot/34RocketMQMQTTQuickStart.md
b/versioned_docs/version-5.0/08-IoT/34RocketMQMQTTQuickStart.md
similarity index 100%
rename from versioned_docs/version-5.0/08-iot/34RocketMQMQTTQuickStart.md
rename to versioned_docs/version-5.0/08-IoT/34RocketMQMQTTQuickStart.md
