Skip to content

fixed #85 require an messageId and send message with it - #87

Open
caoqingguang wants to merge 1 commit into
vert-x3:masterfrom
caoqingguang:master
Open

fixed #85 require an messageId and send message with it#87
caoqingguang wants to merge 1 commit into
vert-x3:masterfrom
caoqingguang:master

Conversation

@caoqingguang

Copy link
Copy Markdown

fixed #85 require an messageId and send message with it, when get ack from remote client , will kown the message is success. if no ack for a long time , i can try again send the same message with the same messageId .

@Sammers21 Sammers21 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments

* @return a reference to this, so the API can be used fluently
*/
@Fluent
MqttEndpoint publishWithId(String topic, Buffer payload, MqttQoS qosLevel, boolean isDup, boolean isRetain,int messageId);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can a message Id generated by hands be useful?

* require an messageId
* @return the next messageId
*/
int requireMessageId();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is a purpose of this?

@ppatierno

Copy link
Copy Markdown
Member

I do think that giving the possibility to the user to set the message-id can lead to a lot of problems even considering that I should review the @Sammers21 PR (I know Pavel ... you hate me ;)) about in-flight messages. The message-id is for internal purpose of the protocol I think that PR #86 makes more sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

how I kown the server publish message (use qos1) is success

4 participants