This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/9.0.x by this push:
     new 6da1604  Wording update - primarily to trigger CI
6da1604 is described below

commit 6da1604561bd21e0dd2127a5046d37ba1df4e5c9
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Wed Aug 19 15:13:45 2020 +0100

    Wording update - primarily to trigger CI
---
 .../examples/WEB-INF/classes/websocket/drawboard/Client.java   | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/webapps/examples/WEB-INF/classes/websocket/drawboard/Client.java 
b/webapps/examples/WEB-INF/classes/websocket/drawboard/Client.java
index 909950d..6d87660 100644
--- a/webapps/examples/WEB-INF/classes/websocket/drawboard/Client.java
+++ b/webapps/examples/WEB-INF/classes/websocket/drawboard/Client.java
@@ -114,9 +114,9 @@ public class Client {
                             // Maybe call this method on another thread.
                             // Note that when this method is called, the 
RemoteEndpoint.Async
                             // is still in the process of sending data, so 
there probably should
-                            // be another way to abort the Websocket 
connection.
-                            // Ideally, there should be some abort() method 
that cancels the
-                            // connection immediately...
+                            // be another way to cancel the Websocket 
connection.
+                            // Ideally, there should be some method that 
cancels the connection
+                            // immediately...
                             session.close(cr);
                         } catch (IOException e) {
                             // Ignore
@@ -203,8 +203,8 @@ public class Client {
                 // other messages.
                 // As a precaution, we close the session (e.g. if a send 
timeout occurred).
                 // TODO: session.close() blocks, while this handler shouldn't 
block.
-                // Ideally, there should be some abort() method that cancels 
the
-                // connection immediately...
+                // Ideally, there should be some method that cancels the 
connection
+                // immediately...
                 try {
                     session.close();
                 } catch (IOException ex) {


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to