Author: kkolinko
Date: Wed Oct 30 11:59:41 2013
New Revision: 1537057
URL: http://svn.apache.org/r1537057
Log:
Review of r1537041:
a pair of typos.
Modified:
tomcat/trunk/java/org/apache/tomcat/websocket/server/WsRemoteEndpointImplServer.java
tomcat/trunk/webapps/docs/web-socket-howto.xml
Modified:
tomcat/trunk/java/org/apache/tomcat/websocket/server/WsRemoteEndpointImplServer.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/websocket/server/WsRemoteEndpointImplServer.java?rev=1537057&r1=1537056&r2=1537057&view=diff
==============================================================================
---
tomcat/trunk/java/org/apache/tomcat/websocket/server/WsRemoteEndpointImplServer.java
(original)
+++
tomcat/trunk/java/org/apache/tomcat/websocket/server/WsRemoteEndpointImplServer.java
Wed Oct 30 11:59:41 2013
@@ -129,7 +129,7 @@ public class WsRemoteEndpointImplServer
protected void doClose() {
if (handler != null) {
// close() can be triggered by a wide range of scenarios. It is far
- // simpler just to always use a dispatch that it is to try and
track
+ // simpler just to always use a dispatch than it is to try and
track
// whether or not this method was called by the same thread that
// triggered the write
clearHandler(new EOFException(), true);
Modified: tomcat/trunk/webapps/docs/web-socket-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/web-socket-howto.xml?rev=1537057&r1=1537056&r2=1537057&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/web-socket-howto.xml (original)
+++ tomcat/trunk/webapps/docs/web-socket-howto.xml Wed Oct 30 11:59:41 2013
@@ -82,7 +82,7 @@
property to <code>true</code> but any explicit setting on the servlet
context
will always take priority.</p>
-<p>The Java WebSocket 1.0 specification requires that call backs for
+<p>The Java WebSocket 1.0 specification requires that callbacks for
asynchronous writes are performed on a different thread to the thread that
initiated the write. Since the container thread pool is not exposed via the
Servlet API, the WebSocket implementation has to provide its own thread
pool.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
