[rocketmq-clients] branch master updated: Docs: amend the part of message id (#14)

[aa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

aaronai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq-clients.git


The following commit(s) were added to refs/heads/master by this push:
     new 4e57c6f  Docs: amend the part of message id (#14)
4e57c6f is described below

commit 4e57c6f02bb5dda868b99d1d6d90eace6393d171
Author: Aaron Ai <ya...@gmail.com>
AuthorDate: Wed Jun 22 23:37:43 2022 +0800

    Docs: amend the part of message id (#14)
---
 docs/message_id.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/message_id.md b/docs/message_id.md
index 0d1ce1a..37c175c 100644
--- a/docs/message_id.md
+++ b/docs/message_id.md
@@ -14,7 +14,7 @@ Both the two types of message identifier have their own shortcomings in the new
 
 For the first type, the new message identifier is not expected to be bound to the persistent information. Considering this scenario: a failure to send message triggers automatic retry, resulting in duplicate message. Since the two messages are exactly the same for client, they should have the same message identifier.
 
-As for the second type, the imperfect algorithm design is the greatest flaw. Specifically, when the client runs for more than a month, the probability of message id repetition will be greatly increased.
+As for the second type, there are some major flaws in the algorithm design. Firstly, some language-specific methods are used to participate in the generation of message identifier. On the other side, when the client runs for more than a month, the probability of message id repetition will be greatly increased.
 
 ## Detailed Design