Author: asmuts
Date: Mon Apr 10 09:57:25 2006
New Revision: 392987
URL: http://svn.apache.org/viewcvs?rev=392987&view=rev
Log:
added additional xdocs for the remote server detailing the client configuration
properties
added to the changes.xml file
Added:
jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml
Modified:
jakarta/jcs/trunk/xdocs/changes.xml
jakarta/jcs/trunk/xdocs/navigation.xml
jakarta/jcs/trunk/xdocs/tasks.xml
Added: jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml
URL:
http://svn.apache.org/viewcvs/jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml?rev=392987&view=auto
==============================================================================
--- jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml (added)
+++ jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml Mon Apr 10 09:57:25 2006
@@ -0,0 +1,138 @@
+<?xml version="1.0"?>
+
+<document>
+ <properties>
+ <title>Remote Cache Configuration</title>
+ <author email="[EMAIL PROTECTED]">Aaron Smuts</author>
+ </properties>
+
+ <body>
+ <section name="Remote Auxiliary Cache Configuration">
+
+ <p>
+ The following properties apply to the Remote
Cache
+ plugin.
+ </p>
+
+ <subsection name="Remote Client Configuration
Properties">
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Description</th>
+ <th>Required</th>
+ <th>Default Value</th>
+ </tr>
+ <tr>
+ <td>FailoverServers</td>
+ <td>
+ This is a comma
separated list of remote
+ servers to use. They
should be specified in
+ the host:port format.
The first server in
+ the list will be used
as the primary server.
+ If the connection is
lost with the primary,
+ the cache will try to
connect to the next
+ server in the list. If
a connection is
+ successfully
established with a failover
+ server, then the cache
will attempt to
+ restore the conenction
with the primary
+ server.
+ </td>
+ <td>Y</td>
+ <td>n/a</td>
+ </tr>
+ <tr>
+ <td>LocalPort</td>
+ <td>
+ This is the port on
which the client will
+ receive callbacks from
the remote server. If
+ it is not spedified,
then some port in the
+ default range used by
RMI will be the
+ callback port.
+ </td>
+ <td>N</td>
+ <td>default RMI port range</td>
+ </tr>
+ <tr>
+ <td>RemoveUponRemotePut</td>
+ <td>
+ If you configure the
cache to remove upon a
+ remote put, this means
that the client will
+ translate updates into
removes. The client
+ will remove any local
copy it has of the
+ object rather than
storing the new version.
+ If you have sticky load
balancing across
+ your client servers,
then it would make sense
+ to set
RemoveUponRemotePut to true if the
+ data is mostly client
specific. If the data
+ is re-usable, the you
should most likely set
+ this option to false,
which is the default.
+ </td>
+ <td>N</td>
+ <td>false</td>
+ </tr>
+ <tr>
+
<td>RmiSocketFactoryTimeoutMillis</td>
+ <td>
+ If this is greater than
0, then a custom
+ socket factory will be
installed in the VM.
+ It will then use this
timeout for all RMI
+ communication.
+ </td>
+ <td>N</td>
+ <td>5000</td>
+ </tr>
+ <tr>
+ <td>GetOnly</td>
+ <td>
+ GetOnly is somewhat
misnamed. If it is set
+ to true, then the
client will not send
+ updates or removes to
the remote server. It
+ can still receive
updates and removes.
+ </td>
+ <td>N</td>
+ <td>false</td>
+ </tr>
+ <tr>
+ <td>Receive</td>
+ <td>
+ By default Receive is
set to true. This
+ means that the remote
client will receive
+ updates and removes
from the remote server.
+ If you set Receive to
false, the remote
+ client will not
register a listener with the
+ remote server. This
means that the client
+ can send update and
remove requests to the
+ server, and it can get
from the server, but
+ it will never receive
notifications from the
+ server. You might
configure Receive to false
+ if you just want to use
the remote server as
+ a data store. For
instance, you may back the
+ Remote Cache Server
with the JDBC disk cache
+ and set Receive=false
when you have a high
+ put and low read region.
+ </td>
+ <td>N</td>
+ <td>true</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="Example Configuration">
+ <source>
+ <![CDATA[
+# This remote client does not receive
+jcs.auxiliary.RC=org.apache.jcs.auxiliary.remote.RemoteCacheFactory
+jcs.auxiliary.RC.attributes=org.apache.jcs.auxiliary.remote.RemoteCacheAttributes
+jcs.auxiliary.RC.attributes.FailoverServers=localhost:1101,localhost:1102
+jcs.auxiliary.RC.attributes.LocalPort=1201
+jcs.auxiliary.RC.attributes.RemoveUponRemotePut=false
+jcs.auxiliary.RC.attributes.RmiSocketFactoryTimeoutMillis=5000
+jcs.auxiliary.RC.attributes.GetOnly=false
+jcs.auxiliary.RC.attributes.Receive=false
+ ]]>
+ </source>
+ </subsection>
+
+ </section>
+ </body>
+</document>
\ No newline at end of file
Modified: jakarta/jcs/trunk/xdocs/changes.xml
URL:
http://svn.apache.org/viewcvs/jakarta/jcs/trunk/xdocs/changes.xml?rev=392987&r1=392986&r2=392987&view=diff
==============================================================================
--- jakarta/jcs/trunk/xdocs/changes.xml (original)
+++ jakarta/jcs/trunk/xdocs/changes.xml Mon Apr 10 09:57:25 2006
@@ -5,6 +5,45 @@
</properties>
<body>
+ <release version="1.2.7.3" date="in CVS">
+ <action dev="asmuts" type="update" due-to="">
+ You can now configure the remote cache client
to not
+ receive from the remote server.
+ </action>
+ <action dev="asmuts" type="update" due-to="">
+ Added a new xdoc for the Remote Cache
properties.
+ </action>
+ </release>
+
+ <release version="1.2.7.2" date="in CVS">
+ <action dev="asmuts" type="update" due-to="">
+ You can configure the remote cache to use a
custom RMI
+ Socket Factory with socket timeouts.
+ </action>
+ <action dev="hchar" type="fix" due-to="">
+ Removed redundant system out logging from
remote cache
+ server.
+ </action>
+ <action dev="asmuts" type="update" due-to="">
+ Added additional stats for remote cache.
+ </action>
+ </release>
+
+ <release version="1.2.7.1" date="in CVS">
+ <action dev="asmuts" type="update" due-to="">
+ Added a JDBC disk cache. It has been tested
with MYSql
+ and HSQL.
+ </action>
+ <action dev="asmuts" type="update" due-to="">
+ Added a special HSQL implementation of the JDBC
disk
+ cache. This replaces the previous experimental
HSQL
+ implementation.
+ </action>
+ <action dev="asmuts" type="update" due-to="">
+ Added a new xdoc for the JDBC Disk Cache
properties.
+ </action>
+ </release>
+
<release version="1.2.7.0" date="in CVS">
<action dev="asmuts" type="update" due-to="">
Removed dependencies on commons-lang and on
Modified: jakarta/jcs/trunk/xdocs/navigation.xml
URL:
http://svn.apache.org/viewcvs/jakarta/jcs/trunk/xdocs/navigation.xml?rev=392987&r1=392986&r2=392987&view=diff
==============================================================================
--- jakarta/jcs/trunk/xdocs/navigation.xml (original)
+++ jakarta/jcs/trunk/xdocs/navigation.xml Mon Apr 10 09:57:25 2006
@@ -48,6 +48,8 @@
<item name="JDBC Disk Properties"
href="/JDBCDiskCacheProperties.html" />
<item name="Remote Cache"
href="/RemoteAuxCache.html" />
+ <item name="Remote Cache Properties"
+ href="/RemoteCacheProperties.html" />
<item name="Lateral TCP Cache"
href="/LateralTCPAuxCache.html" />
<item name="Lateral TCP Properties"
Modified: jakarta/jcs/trunk/xdocs/tasks.xml
URL:
http://svn.apache.org/viewcvs/jakarta/jcs/trunk/xdocs/tasks.xml?rev=392987&r1=392986&r2=392987&view=diff
==============================================================================
--- jakarta/jcs/trunk/xdocs/tasks.xml (original)
+++ jakarta/jcs/trunk/xdocs/tasks.xml Mon Apr 10 09:57:25 2006
@@ -16,36 +16,18 @@
coding guidelines</a> established for Turbine family of projects.
</p>
<ul>
- <li>Turbine service for JCS</li>
- <li>XML-RPC lateral cache completion</li>
- <li>Javagroups lateral cache</li>
- <li>Applet or command line XML-RPC monitor client</li>
- <li>Session distribution testing</li>
<li>Examples</li>
<li>XML config</li>
<li>
Run-time auxiliary selection (establish all lateral
- available and choose via access)</li> <li>Idle time check in
+ available and choose via access)</li>
+ <li>Idle time check in
hub on get ( only check maxLife expiration now)
</li>
- <li>Memory shrinker improvements</li>
- <li>More structured documentation</li>
- <li>
- Rename Composite cache to CacheHub and
- CompositeCacheAttributes</li>
- <li>
- ElementAttributes copy -- maybe create new constructor, avoid
- methods
- </li>
- <li>Torque JCS integration</li>
<li>LFU memory cache</li>
- <li>Lateral Token ring locking</li>
- <li>Cluster architecture proposals</li>
<li>JUnit tests</li>
<li>Embedded servlet options</li>
<li>JMS lateral cache</li>
- <li>Disk and lateral cache refactoring</li>
- <li>Profile LinkedQueue -- the faster the better</li>
</ul>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
