# HG changeset patch # User chegar # Date 1528714526 -3600 # Node ID bd76f0daf3c24d8f633a3e36055fed885ce63883 # Parent d219df0c7d2456a57ed62f586223d916631921ae http-client-branch: review comment: minor editorial change to WebSocket.Listener diff -r d219df0c7d24 -r bd76f0daf3c2 src/java.net.http/share/classes/java/net/http/WebSocket.java --- a/src/java.net.http/share/classes/java/net/http/WebSocket.java Thu Jun 07 14:21:50 2018 +0100 +++ b/src/java.net.http/share/classes/java/net/http/WebSocket.java Mon Jun 11 11:55:26 2018 +0100 @@ -238,11 +238,11 @@ * exceptionally, the WebSocket will invoke {@code onError} with this * exception. * - * @apiNote

The strict sequential order of invocations from - * {@code WebSocket} to {@code Listener} means, in particular, that - * {@code Listener}'s methods are treated as non-reentrant. Which means that + * @apiNote The strict sequential order of invocations from + * {@code WebSocket} to {@code Listener} means, in particular, that the + * {@code Listener}'s methods are treated as non-reentrant. This means that * {@code Listener} implementations do not need to be concerned with - * possible recursion or the order in which they call + * possible recursion or the order in which they invoke * {@code WebSocket.request} in relation to their processing logic. * *

Careful attention may be required if a listener is associated