This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit d55413fb9bfc25518550b7be470bbc5c23ccad5c
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Wed Jan 25 15:40:32 2023 +0000
Add missing <p> tags
---
java/org/apache/coyote/http2/WindowAllocationManager.java | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/java/org/apache/coyote/http2/WindowAllocationManager.java
b/java/org/apache/coyote/http2/WindowAllocationManager.java
index 45ac2fdbfd..47d0d1ac1f 100644
--- a/java/org/apache/coyote/http2/WindowAllocationManager.java
+++ b/java/org/apache/coyote/http2/WindowAllocationManager.java
@@ -28,22 +28,22 @@ import org.apache.tomcat.util.res.StringManager;
* allocation and only issues allocation notifications when the stream is known
* to be waiting for the notification.
*
- * It is possible for a stream to be waiting for a connection allocation when
+ * <p>It is possible for a stream to be waiting for a connection allocation
when
* a stream allocation is made. Therefore this class tracks the type of
* allocation that the stream is waiting for to ensure that notifications are
* correctly triggered.
*
- * With the implementation at the time of writing, it is not possible for a
+ * <p>With the implementation at the time of writing, it is not possible for a
* stream to receive an unexpected connection notification as these are only
* issues to streams in the backlog and a stream must be waiting for a
* connection allocation in order to be placed on the backlog. However, as a
* precaution, this class protects against unexpected connection notifications.
*
- * It is important for asynchronous processing not to notify unless a
+ * <p>It is important for asynchronous processing not to notify unless a
* notification is expected else a dispatch will be performed unnecessarily
* which may lead to unexpected results.
*
- * A previous implementation used separate locks for the stream and connection
+ * <p>A previous implementation used separate locks for the stream and
connection
* notifications. However, correct handling of allocation waiting requires
* holding the stream lock when making the decision to wait. Therefore both
* allocations need to wait on the Stream.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
