doc(iot-serv): Add documentation to fileuploadNotificationReceiver about QoS #619
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…out QoS All receive operations have a QoS of 1, but that wasn't documented before
|
/azp run Java Canary |
|
/azp run SDL |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Java Canary Basic |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Java Prod Basic |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
bikamani
reviewed
Nov 7, 2019
| @@ -75,6 +75,8 @@ public void close() throws IOException | |||
| /** | |||
| * Receive FileUploadNotification with default timeout | |||
There was a problem hiding this comment.
It would be good to document default timeout as well.
bikamani
approved these changes
Nov 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All receive operations have a QoS of 1, but that wasn't documented before