costin 2002/10/03 09:57:49
Modified: jk/xdocs index.xml
jk/xdocs/jk2 configwebcom.xml
Log:
Added the 'version' common property.
Few addition and fixes in the description of jk2.
Revision Changes Path
1.11 +23 -7 jakarta-tomcat-connectors/jk/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/index.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- index.xml 23 Sep 2002 14:59:39 -0000 1.10
+++ index.xml 3 Oct 2002 16:57:49 -0000 1.11
@@ -13,7 +13,7 @@
It was a completely new Tomcat-Apache plug-in that handles the communication
between Tomcat and Apache.
</p>
<p>
-The newest <b>JK2</b> is a rewrite of <b>JK</b>.
+The newest <b>JK2</b> is a refactoring of <b>JK</b>.
The native part has been completly
restructured and the configuration has been simplified a lot.
</p>
@@ -75,19 +75,35 @@
<section name="What's the difference between JK and JK2 ?">
<p>
-JK2 is a full rewrite of JK and is much more powerfull.
+JK2 is a refactoring of JK and is much more powerfull.
</p>
<p>
Even if it works with Apache 1.3, JK2 has been developed with Apache 2.0 in mind,
-and sus is better suited for multi-threaded servers like IIS, NES/iPlanet.
+and is better suited for multi-threaded servers like IIS, NES/iPlanet. It can also
+be embeded in other applications and used from java.
</p>
<p>
-JK2 has a better separation between protocol and physical layer.
+JK2 improves the modularity and has a better separation between protocol and
physical layer.
As such JK2 support fast unix-socket, and could be extended to support others
communications
-channels. Better it's suited for JNI and JDK 1.4 fast IO APIs
+channels. It is better suited for JNI and may use (in a future version) JDK 1.4 NIO.
</p>
<p>
-JK2 could be monitored via special URLs (like mod_status)
+There is additional support for monitoring, similar with JMX in java. A module
similar
+with mod_status is provided, and additional adapters can be used to interface and
+provide status and runtime configuration. .
+</p>
+<p>
+The configuration has been changed to follow the component models. Multiple
configuration
+sources can be supported ( in additon to file ) providing better integration with
+the embeding application. The config layer uses the management layer APIs and it can
+support persistence for changes done via runtime configuration.
+</p>
+<p>
+Another feature is the JNI mode. Jk2 can be used as a JNI library and provide
access to
+native features to java. For example it provides access to shared memory ( used for
+config and monitoring in a multiprocess environment ), unix domain sockets. It can
+also provide access to signals, chuid, win registry. All using the same
communication
+mechansim, and supporting both in-process and out-of process modes.
</p>
</section>
1.2 +11 -2 jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml
Index: configwebcom.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- configwebcom.xml 3 Oct 2002 15:33:41 -0000 1.1
+++ configwebcom.xml 3 Oct 2002 16:57:49 -0000 1.2
@@ -31,8 +31,17 @@
<tr>
<td>debug</td>
<td>0 (false)</td>
- <td>"debug" state for the component, 1=true 0=false</td>
+ <td>Debug level for the component, 0=disabled, 1..10
enabled. Higher levels
+ generate more debug.</td>
</tr>
+ <tr>
+ <td>version</td>
+ <td>0</td>
+ <td>'Generation' of the component config. Important for
runtime reconfiguration.
+ If you edit the config file or set the shmem
properties, you need to also
+ upgrade the version of the modified component. The
config layer will detect
+ the change and call the setter method.</td>
+ </tr>
</table>
</p>
</section>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
