You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Improve session message injection methods
* Add more tests for session injection
* Change return type from MqttPublishPacket to MqttPacketWithIdentifier
* Use dedicated type for MattApplicationMessage injection result
* Code review minor fixes
* Apply project code style
* Update release notes
---------
Co-authored-by: Anton Smolkov <[email protected]>
Co-authored-by: christian <[email protected]>
/// Attempts to enqueue an application message to the session's send buffer.
71
+
/// </summary>
72
+
/// <param name="applicationMessage">The application message to enqueue.</param>
73
+
/// <param name="injectResult"><see cref="InjectMqttApplicationMessageResult"/> that includes the packet identifier of the enqueued message.</param>
74
+
/// <returns><c>true</c> if the message was successfully enqueued; otherwise, <c>false</c>.</returns>
75
+
/// <remarks>
76
+
/// When <see cref="MqttServerOptions.PendingMessagesOverflowStrategy"/> is set to <see cref="MqttPendingMessagesOverflowStrategy.DropOldestQueuedMessage"/>,
77
+
/// this method always returns <c>true</c>.
78
+
/// However, an existing message in the queue may be <b>dropped later</b> to make room for the newly enqueued message.
79
+
/// Such dropped messages can be tracked by subscribing to <see cref="MqttServer.QueuedApplicationMessageOverwrittenAsync"/> event.
0 commit comments