svn commit: r1577884 - /tomcat/trunk/webapps/docs/config/http.xml

[kk...@apache.org]

Author: kkolinko
Date: Sat Mar 15 15:36:13 2014
New Revision: 1577884

URL: http://svn.apache.org/r1577884
Log:
Followup to r1577831
Clarify the new socket.directSslBuffer option.

Modified:
    tomcat/trunk/webapps/docs/config/http.xml

Modified: tomcat/trunk/webapps/docs/config/http.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/http.xml?rev=1577884&r1=1577883&r2=1577884&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/http.xml (original)
+++ tomcat/trunk/webapps/docs/config/http.xml Sat Mar 15 15:36:13 2014
@@ -815,9 +815,13 @@
 
       <attribute name="socket.directSslBuffer" required="false">
         <p>(bool)Boolean value, whether to use direct ByteBuffers or java mapped
-        ByteBuffers for the SSL buffers. Default is <code>false</code>.<br/>
+        ByteBuffers for the SSL buffers. If <code>true</code> then
+        <code>java.nio.ByteBuffer.allocateDirect()</code> is used to allocate
+        the buffers, if <code>false</code> then
+        <code>java.nio.ByteBuffer.allocate()</code> is used. The default value
+        is <code>false</code>.<br/>
         When you are using direct buffers, make sure you allocate the
-        appropriate amount of memory for the direct memory space. On Sun's JDK
+        appropriate amount of memory for the direct memory space. On Oracle's JDK
         that would be something like <code>-XX:MaxDirectMemorySize=256m</code>.
         </p>
       </attribute>



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