You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by Henning Schmiedehausen <he...@apache.org> on 2005/02/09 10:24:08 UTC
[PROPOSAL + VOTE] Promotion of the JCS Project to become a regular
Jakarta Member
[I'm sending this proposal on behave of the JCS people who currently
don't have any active committer on the PMC].
--- cut ---
Proposal for JCS Project Promotion
I. Rational
JCS (Java Caching System) was the one of, if not the first, major open-
source Java caching solution. After a few years of incubation within
the Turbine project, JCS is ready to become a top-level Jakarta project.
The scope and maturity of JCS make it suitable for top level project
status.
The JCS project is of the scope of projects such as Velocity and Lucene,
which its sub project status does not indicate. Since JCS has no
dependencies on Turbine, it would less confusing to users if it were its
own top-level project. Given the size and coherence of the code-base it
is not well suited in as a module of any other project, such as
commons.
JCS is ready for a production release. Over the past year, we solved
all major, known bugs. Although there are a growing number of
competitors, JCS has a good number of users and is currently at a 1.2.4
development version.
JCS would be a good addition to the list of current top level Jakarta
projects, and, perhaps more importantly, it would benefit from the input
of a larger community that increased exposure would afford.
II. Scope of the Package
JCS is a distributed caching system written in java for server-side or
standalone java applications. The project is an attempt to build a
system close to JCACHE , JSR-107, a description of the caching system
used in Oracle9i. JCS is intended to speed up dynamic web applications
by providing a means to manage cached data of various dynamic natures.
Like any caching system, JCS is most useful for high read, low put
applications.
JCS is essentially a cache hub and several production-ready and
experimental modules that can be plugged into the hub. In JCS, cached
data is stored in a region. Each region can be configured independently
of the others. JCS is modeled on log4j, where various
appenders can be defined for specific regions.
JCS defines four types of appenders, or what we call auxiliaries:
memory, disk, lateral, and remote. A memory auxiliary manages items
stored in memory. Disk auxiliaries manage memory overflow and
persistence of cached data. Lateral auxiliaries communicate directly
with other caches. Remote auxiliaries communicate with a remote server
to which other caches are connected. At least one production ready
implementation of each type of auxiliary is included in the core JCS
jar. The LRU memory cache, indexed disk cache, TCP lateral cache,
JGroups lateral cache, and RMI remote cache auxiliaries form the core
suite of stable JCS auxiliaries.
JCS is extremely configurable. Every auxiliary exposes detailed
configuration options. For example, the indexed disk cache allows you
to configure such things as the maximum number of keys in memory, the
size of the recycle bin for reusing empty spots on disk, whether it
should defragment and if so when, and the type of event queue to use.
More information on the available disk cache configuration options can
be found here:
http://jakarta.apache.org/turbine/jcs/IndexedDiskAuxCache.html
One of the most important features of JCS is that you can plug in new
auxiliaries. Each type of auxiliary has a defined interface, and the
implementation class can be defined in the JCS configuration file.
The cache hub and the core auxiliaries are contained in a JAR file that
is JDK 1.3 compatible. Other JDK 1.4 specific features are contained in
another optional JAR.
JCS also has an active sandbox, where a prototype cache that heavily
makes use of JDK 1.5 features is being developed.
III. Interaction with other packages
JCS has dependencies on several standard commons packages, including:
commons-lang, commons-collections, and commons-logging. We also
depend on Doug Lea's util concurrent JAR for some of our locking and
thread pools. Some of the optional auxiliaries depend on other
libraries. For instance, the JGroups jar depends on the JGroups
release. The, JDK 1.4 optional, Berkeley DB auxiliary depends on the
related project.
The Cocoon project currently uses JCS as its caching mechanism.
IV. Source of the package
I contributed JCS to the Stratum project, a subproject of Turbine, over
three years ago. It has been a sub project of Turbine for about 2
years.
V. Base name for the package
The JCS code is currently checked into CVS with the following root
package name:
org.apache.jcs
VI. Coding conventions
The code follows a modified version of Sun's standard coding
conventions, with the following stylistic changes:
* instance variables are prefixed with an underscore
* a newline is inserted before all braces
VII. Jakarta resources to be created
The current mailing lists are turbine-jcs-user@jakarta.apache.org and
turbine-jcs-dev@jakarta.apache.org. We should forward these lists to,
or just create, these two new lists:
jcs-user@jakarta.apache.org -- User discussions
jcs-dev@jakarta.apache.org -- Developer discussions and CVS update
notifications
VIII. Initial set of committers
There are currently four committers on the JCS project, all of whom have
licenses on file.
Aaron Smuts <as...@apache.org>
James Taylor <ja...@jamestaylor.org>
Hanson Char <hc...@apache.org>
Travis Savo <ts...@IFILM.com>
There are also several active contributors to the project.
VIII. Documentation
You can find the current Maven generated JCS documentation here:
http://jakarta.apache.org/turbine/jcs/
--- cut ---
+1 [ ] Cool, I think JCS should be a Jakarta Project
0 [ ] I don't care
-1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
RE: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regular
Jakarta Member
Posted by Aaron Smuts <aa...@wisc.edu>.
Of course, the proposal has my +1 too. Thanks submitting this to the
PMC.
Aaron
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Wednesday, February 09, 2005 8:19 AM
> To: turbine-jcs-dev@jakarta.apache.org
> Subject: Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become
a
> regular Jakarta Member
>
> Hanson Char <ha...@gmail.com> writes:
>
> >+1 [X] Cool, I think JCS should be a Jakarta Project
>
> Hi,
>
> thanks, I'll record that. The actual vote is held on the PMC list; I
> just Cc'ed the vote kickoff to jcs-dev so that you guys know what is
> going on.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development -- hero for
hire
> Linux, Java, perl, Solaris -- Consulting, Training, Development
>
> What is more important to you...
> [ ] Product Security
> or [ ] Quality of Sales and Marketing Support
> -- actual question from a Microsoft customer survey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regular Jakarta Member
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Hanson Char <ha...@gmail.com> writes:
>+1 [X] Cool, I think JCS should be a Jakarta Project
Hi,
thanks, I'll record that. The actual vote is held on the PMC list; I
just Cc'ed the vote kickoff to jcs-dev so that you guys know what is
going on.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regular Jakarta Member
Posted by Hanson Char <ha...@gmail.com>.
+1 [X] Cool, I think JCS should be a Jakarta Project
Hanson
On Wed, 09 Feb 2005 10:28:33 +0100, Henning Schmiedehausen
<he...@apache.org> wrote:
> On Wed, 2005-02-09 at 10:24 +0100, Henning Schmiedehausen wrote:
>
> > +1 [X] Cool, I think JCS should be a Jakarta Project
> > 0 [ ] I don't care
> > -1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development
> Linux, Java, perl, Solaris -- Consulting, Training, Engineering
>
> What is more important to you...
> [ ] Product Security
> or [ ] Quality of Sales and Marketing Support
> -- actual question from a Microsoft customer survey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a
regular Jakarta Member
Posted by Henning Schmiedehausen <he...@apache.org>.
On Wed, 2005-02-09 at 10:24 +0100, Henning Schmiedehausen wrote:
> +1 [X] Cool, I think JCS should be a Jakarta Project
> 0 [ ] I don't care
> -1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a
regular Jakarta Member
Posted by Henning Schmiedehausen <he...@apache.org>.
On Thu, 2005-02-10 at 08:11 +1100, Paul Smith wrote:
> +1 [X ] Cool, I think JCS should be a Jakarta Project
> 0 [ ] I don't care
> -1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
>
>
> Bringing it out of obscurity will encourage both it's exposure to the
> world, and increase the likelihood of others getting involved.
>
> Nice proposal text by the way, great history, enjoyed reading it .
Hi,
all credits here belong to Aaron Smuts. I was just sending it out.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regular
Jakarta Member
Posted by Paul Smith <ps...@apache.org>.
+1 [X ] Cool, I think JCS should be a Jakarta Project
0 [ ] I don't care
-1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
Bringing it out of obscurity will encourage both it's exposure to the
world, and increase the likelihood of others getting involved.
Nice proposal text by the way, great history, enjoyed reading it .
cheers,
Paul
Henning Schmiedehausen wrote:
>[I'm sending this proposal on behave of the JCS people who currently
>don't have any active committer on the PMC].
>
>--- cut ---
>Proposal for JCS Project Promotion
>
>I. Rational
>JCS (Java Caching System) was the one of, if not the first, major open-
>source Java caching solution. After a few years of incubation within
>the Turbine project, JCS is ready to become a top-level Jakarta project.
>The scope and maturity of JCS make it suitable for top level project
>status.
>
>The JCS project is of the scope of projects such as Velocity and Lucene,
>which its sub project status does not indicate. Since JCS has no
>dependencies on Turbine, it would less confusing to users if it were its
>own top-level project. Given the size and coherence of the code-base it
>is not well suited in as a module of any other project, such as
>commons.
>
>JCS is ready for a production release. Over the past year, we solved
>all major, known bugs. Although there are a growing number of
>competitors, JCS has a good number of users and is currently at a 1.2.4
>development version.
>
>JCS would be a good addition to the list of current top level Jakarta
>projects, and, perhaps more importantly, it would benefit from the input
>of a larger community that increased exposure would afford.
>
>
>II. Scope of the Package
>JCS is a distributed caching system written in java for server-side or
>standalone java applications. The project is an attempt to build a
>system close to JCACHE , JSR-107, a description of the caching system
>used in Oracle9i. JCS is intended to speed up dynamic web applications
>by providing a means to manage cached data of various dynamic natures.
>Like any caching system, JCS is most useful for high read, low put
>applications.
>
>JCS is essentially a cache hub and several production-ready and
>experimental modules that can be plugged into the hub. In JCS, cached
>data is stored in a region. Each region can be configured independently
>of the others. JCS is modeled on log4j, where various
>appenders can be defined for specific regions.
>
>JCS defines four types of appenders, or what we call auxiliaries:
>memory, disk, lateral, and remote. A memory auxiliary manages items
>stored in memory. Disk auxiliaries manage memory overflow and
>persistence of cached data. Lateral auxiliaries communicate directly
>with other caches. Remote auxiliaries communicate with a remote server
>to which other caches are connected. At least one production ready
>implementation of each type of auxiliary is included in the core JCS
>jar. The LRU memory cache, indexed disk cache, TCP lateral cache,
>JGroups lateral cache, and RMI remote cache auxiliaries form the core
>suite of stable JCS auxiliaries.
>
>JCS is extremely configurable. Every auxiliary exposes detailed
>configuration options. For example, the indexed disk cache allows you
>to configure such things as the maximum number of keys in memory, the
>size of the recycle bin for reusing empty spots on disk, whether it
>should defragment and if so when, and the type of event queue to use.
>More information on the available disk cache configuration options can
>be found here:
>http://jakarta.apache.org/turbine/jcs/IndexedDiskAuxCache.html
>
>One of the most important features of JCS is that you can plug in new
>auxiliaries. Each type of auxiliary has a defined interface, and the
>implementation class can be defined in the JCS configuration file.
>
>The cache hub and the core auxiliaries are contained in a JAR file that
>is JDK 1.3 compatible. Other JDK 1.4 specific features are contained in
>another optional JAR.
>
>JCS also has an active sandbox, where a prototype cache that heavily
>makes use of JDK 1.5 features is being developed.
>
>III. Interaction with other packages
>JCS has dependencies on several standard commons packages, including:
>commons-lang, commons-collections, and commons-logging. We also
>depend on Doug Lea's util concurrent JAR for some of our locking and
>thread pools. Some of the optional auxiliaries depend on other
>libraries. For instance, the JGroups jar depends on the JGroups
>release. The, JDK 1.4 optional, Berkeley DB auxiliary depends on the
>related project.
>
>The Cocoon project currently uses JCS as its caching mechanism.
>
>IV. Source of the package
>I contributed JCS to the Stratum project, a subproject of Turbine, over
>three years ago. It has been a sub project of Turbine for about 2
>years.
>
>V. Base name for the package
>The JCS code is currently checked into CVS with the following root
>package name:
>org.apache.jcs
>
>VI. Coding conventions
>The code follows a modified version of Sun's standard coding
>conventions, with the following stylistic changes:
>* instance variables are prefixed with an underscore
>* a newline is inserted before all braces
>
>VII. Jakarta resources to be created
>The current mailing lists are turbine-jcs-user@jakarta.apache.org and
>turbine-jcs-dev@jakarta.apache.org. We should forward these lists to,
>or just create, these two new lists:
>jcs-user@jakarta.apache.org -- User discussions
>jcs-dev@jakarta.apache.org -- Developer discussions and CVS update
>notifications
>
>VIII. Initial set of committers
>There are currently four committers on the JCS project, all of whom have
>licenses on file.
>Aaron Smuts <as...@apache.org>
>James Taylor <ja...@jamestaylor.org>
>Hanson Char <hc...@apache.org>
>Travis Savo <ts...@IFILM.com>
>
>There are also several active contributors to the project.
>
>VIII. Documentation
>You can find the current Maven generated JCS documentation here:
>http://jakarta.apache.org/turbine/jcs/
>--- cut ---
>
>+1 [ ] Cool, I think JCS should be a Jakarta Project
> 0 [ ] I don't care
>-1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
>
> Regards
> Henning
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a
regular Jakarta Member
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
It is a Jakarta-Turbine project currently. :-)
Regards
Henning
On Fri, 2005-02-11 at 10:29 -0500, Vadim Gritsenko wrote:
> Henning Schmiedehausen wrote:
> > +1 [X] Cool, I think JCS should be a Jakarta Project
>
> For some reason I thought it already is a jakarta project...
>
>
> PS We've seen some issues with jcs at cocoon-land, don't remember details...
>
> Vadim
>
>
> > 0 [ ] I don't care
> > -1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
> >
> > Regards
> > Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
Re: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regular
Jakarta Member
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Henning Schmiedehausen wrote:
> +1 [X] Cool, I think JCS should be a Jakarta Project
For some reason I thought it already is a jakarta project...
PS We've seen some issues with jcs at cocoon-land, don't remember details...
Vadim
> 0 [ ] I don't care
> -1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
>
> Regards
> Henning
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
[RESULT] Promotion of the JCS Project to become a regular Jakarta
Member
Posted by Henning Schmiedehausen <he...@apache.org>.
On Wed, 2005-02-09 at 10:24 +0100, Henning Schmiedehausen wrote:
> Proposal for JCS Project Promotion
[...]
Ok, 72 hour voting period is over.
+1 Aaron Smuts <aa...@wisc.edu>
+1 Dion Gillard <di...@gmail.com>
+1 Eric Pugh <ep...@upstate.com>
+1 Henning Schmiedehausen <he...@apache.org>
+1 Henri Yandell <ba...@generationjava.com>
+1 Jeanfrancois Arcand <jf...@apache.org>
+1 Martin van den Bemt <ma...@mvdb.net>
+1 Paul Smith <ps...@apache.org>
+1 Scott Eade <se...@backstagetech.com.au>
+1 Travis Savo <ts...@IFILM.com>
+1 Vadim Gritsenko <va...@reverycodes.com>
+1 Yoav Shapira <yo...@apache.org>
+1 robert burrell donkin <rd...@apache.org>
+1 Hanson Char <ha...@gmail.com>
No 0 or -1 votes. At least three PMC members have voted.
So the vote passes. Congratulations to the JCS team for graduation to
"Jakarta JCS".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org
RE: [PROPOSAL + VOTE] Promotion of the JCS Project to become a regularJakarta Member
Posted by Eric Pugh <ep...@upstate.com>.
+1 [X ] Cool, I think JCS should be a Jakarta Project
0 [ ] I don't care
-1 [ ] Nah, JCS should stay in obscurity hidden behind Turbine
That was a very nicely worded summary!
*********************************************************************************************************
The information in this email is confidential and may be legally privileged. Access
to this email by anyone other than the intended addressee is unauthorized. If you are
not the intended recipient of this message, any review, disclosure, copying,
distribution, retention, or any action taken other than notification to sender and
deletion is prohibited and may be unlawful. If you are not the intended recipient,
please reply to or forward a copy of this message to the sender and delete the message,
any attachments, and any copies from your system.
*********************************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org