Split the held-message bounds and the shutdownTimeout fallback into decisions of their own, and drop what code and README say
Test / test (20) (pull_request) Successful in 32s
Test / test (24) (pull_request) Successful in 38s
Mirror / push (push) Successful in 7s
Test / lint (pull_request) Successful in 29s
Test / test (18) (pull_request) Successful in 33s
Test / test (22) (pull_request) Successful in 32s
Test / test (26) (pull_request) Successful in 32s

This commit was merged in pull request #28.
This commit is contained in:
2026-09-25 19:32:59 +02:00
parent dba95d9524
commit d8232bcd67
2 changed files with 21 additions and 26 deletions
+2
View File
@@ -301,6 +301,8 @@ the file.
request that handling did not answer.
- The drain waits on the messages the application holds, and `sendResp()` is what says it is done
with one.
- The drain's wait on the application ignores `shutdownTimeout: 0`.
- What the application holds unanswered is capped on constants.
- A reconnect keeps the delivery-receipt merges; everything else the link held is dropped.
- A message id base is merged at most once.
- A send that never reached the socket waits for the next link; one that did is counted, not resent.