madru Active Member Licensed User Longtime User Jul 19, 2017 #1 Hi, looks like that the messagid is always set to 0 if subscribing > QoS=0, can somebody confirm and/or verify? THX Attachments Untitled.png 21 KB · Views: 231 Untitled1.png 145.6 KB · Views: 223
Hi, looks like that the messagid is always set to 0 if subscribing > QoS=0, can somebody confirm and/or verify? THX
Erel B4X founder Staff member Licensed User Longtime User Jul 19, 2017 #2 The message id is managed by the Paho open source project. You need to check it there. Upvote 0
madru Active Member Licensed User Longtime User Jul 19, 2017 #3 yes, the Paho native client shows the correct behaviour Client mosqsub/6782-Asmo received PUBLISH (d0, q1, r0, m13, 'test', ... (5 bytes)) Client mosqsub/6782-Asmo sending PUBACK (Mid: 13) I haven't verified if they are based on the library Upvote 0
yes, the Paho native client shows the correct behaviour Client mosqsub/6782-Asmo received PUBLISH (d0, q1, r0, m13, 'test', ... (5 bytes)) Client mosqsub/6782-Asmo sending PUBACK (Mid: 13) I haven't verified if they are based on the library
Erel B4X founder Staff member Licensed User Longtime User Jul 20, 2017 #4 What is the problem? Upvote 0
madru Active Member Licensed User Longtime User Jul 20, 2017 #5 messageId is always set to 0, in the paho native client you can see the counting ID's correctly. found an old thread with the same problem, .....not sure which version you have wrapped Upvote 0
messageId is always set to 0, in the paho native client you can see the counting ID's correctly. found an old thread with the same problem, .....not sure which version you have wrapped
Erel B4X founder Staff member Licensed User Longtime User Jul 20, 2017 #6 Based on the last comment there it is 0 in the latest version as well (though the commenter might be wrong). What are you using the message id for? It is not exposed in the library. Upvote 0
Based on the last comment there it is 0 in the latest version as well (though the commenter might be wrong). What are you using the message id for? It is not exposed in the library.
madru Active Member Licensed User Longtime User Jul 20, 2017 #7 plan was to identify which message a PUBACK (or PUBREC/PUBREL/PUBCOMP for QoS 1/2) is referring to as we can have multiple messages "in flight" at once. also MessageId=0 is reserved as an invalid Message ID. http://docs.solace.com/MQTT-311-Prtl-Conformance-Spec/MQTT Control Packet format.htm Upvote 0
plan was to identify which message a PUBACK (or PUBREC/PUBREL/PUBCOMP for QoS 1/2) is referring to as we can have multiple messages "in flight" at once. also MessageId=0 is reserved as an invalid Message ID. http://docs.solace.com/MQTT-311-Prtl-Conformance-Spec/MQTT Control Packet format.htm
Erel B4X founder Staff member Licensed User Longtime User Jul 20, 2017 #8 You don't need to do anything special to send multiple messages at once. The client library handles it properly. Upvote 0
You don't need to do anything special to send multiple messages at once. The client library handles it properly.