Re: [POLL] Future Of Turbine-JCS
So far it sounds to me like JCS is only used by Turbine and that only the Turbiners really care about it. Thus I don't see why it doesn't just get flattened into Turbine and just consider it one more turbine service. However, if it DOES have a community or at the very least someone who loves cares and feeds it, then commons sounds like a reasonable place to build a community. As far as oversight, who on the PMC is on this sub-sub-subproject? From a Jakarta PMC perspective, I think that we should cease to support Sub-sub-projects with the exception of commons.* -Andy * before it is mentioned, on POI we call POIFS and HSSF subprojects but they're really just components. They're called subprojects by tradition, granted it is ambiguous but I'll leave language pedantry to RMS. ;-) On 12/4/03 12:59 PM, Henri Yandell [EMAIL PROTECTED] wrote: So your preference, as the development-community of JCS, is for a top-level-jakarta project, ie) at the log4j level? If so, we can take that up with the PMC and see what views there are. As the development community, your (and James) views count a lot, though the smallness of community is the worrying thing. Hen On Thu, 4 Dec 2003, Aaron Smuts wrote: The core of JCS is ready for a release. The project is basically a hub for 4 types of plugins, or what are called auxiliaries in JCS: memory, disk, lateral distribution, and remote sever. It requires that you use a memory plugin, but the others are optional. For each type of plugin there is an efficient implementation that people are using. These include: LRU memory manager, indexed disk cache, TCp lateral distribution, and RMI remote server. There are experimental versions of each type of plugin in an experimental source directory: a b-tree disk cache, a database disk cache, a javagroups lateral, a MRU memory manager, and others. The core of JCS is then the hub and these 4 non-experimental plugins. Currently there is only one small bug in the lateral cache recovery process, that I will fix very soon. There are additional features that are mostly extensions of the plugins. I wanted to clean up the group handling features, but this is not crucial. I wanted to add run time defragmentation to the indexed disk cache. I also want to implement clustering on the remote server. Basically, this will involve hooking up remote servers via the TCP lateral cache. All that has to be done is to work out a way to prevent circular calls for there to be clustering. The client can already fail over. I'm not sure what all the levels are called, but if we put JCS at the level of log4j, I guess as a jakarta subproject, and then issue a release, we can find out what else people might want and some more people may be interested in contributing. JCS does not need an overhaul or any significant amount of work on the core features. Most conceivable future development will involve tuning, bug fixes, improving configuration, creating sample applications, and extension development. Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Future Of Turbine-JCS
On Thu, 2003-12-04 at 23:35, Andrew C. Oliver wrote: So far it sounds to me like JCS is only used by Turbine and that only the Turbiners really care about it. Thus I don't see why it doesn't just get flattened into Turbine and just consider it one more turbine service. +--+ | Don't | | feed the | | Troll! | +--+ || || || / \__ Come on Andrew, even you can do better than that! Obviously you haven't read s single article in this thread, did you?. JCS is neither a Turbine Service, nor is it used by Turbine at all. The fact that it has been developed under the Turbine label, well it just happened. But JCS neither depends on Turbine nor the other way round. So IMHO it is time to move this (IMHO quite decent) project to a place where it gets much more attention. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de/ Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Future Of Turbine-JCS
Andrew C. Oliver wrote: So far it sounds to me like JCS is only used by Turbine and that only the Turbiners really care about it. it is indirectly used by turbine ... that's why the discussion started ... it is used by torque, ojb, hibernate, ok, they are all db related .. but i still do not think jcs is db related .. Thus I don't see why it doesn't just get flattened into Turbine and just consider it one more turbine service. please go to the jcs site and RTFM However, if it DOES have a community or at the very least someone who loves cares and feeds it, then commons sounds like a reasonable place to build a community. As far as oversight, who on the PMC is on this sub-sub-subproject? i am From a Jakarta PMC perspective, I think that we should cease to support Sub-sub-projects with the exception of commons.* we should only support sub-sub project if there is a strong relation to the sub-project ... e.g turbine-fulcrum (avalon components for turbine) -Andy * before it is mentioned, on POI we call POIFS and HSSF subprojects but they're really just components. They're called subprojects by tradition, granted it is ambiguous but I'll leave language pedantry to RMS. ;-) what is the definition of a sub-sub project?? martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Karma for Jakarta main web site
As indicated on http://jakarta.apache.org/site/jakarta-site2b.html I like to get CVS Karma to update the Jakarta main web site. Could someone grant me that Karma, please? Thanks in advance :) Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Karma for Jakarta main web site
On Dec 5, 2003, at 3:52 AM, Oliver Zeigermann wrote: As indicated on http://jakarta.apache.org/site/jakarta-site2b.html I like to get CVS Karma to update the Jakarta main web site. Could someone grant me that Karma, please? Done. Be good. geir Thanks in advance :) Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Geir Magnusson Jr 203-247-1713(m) [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Karma for Jakarta main web site
Geir Magnusson Jr. wrote: On Dec 5, 2003, at 3:52 AM, Oliver Zeigermann wrote: As indicated on http://jakarta.apache.org/site/jakarta-site2b.html I like to get CVS Karma to update the Jakarta main web site. Could someone grant me that Karma, please? Done. Be good. I will! Just wanted to add my name and bio to the committers list :) Thanks, Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] VPP 2.0.0 just released
VPP, the Velocity Preprocessor, has just released version 2.0.0. VPP provides general file preprocessing support based on the Velocity Template Engine and Ant. The core funtionality is provided as a filter for use with tasks that supports filter chains. Also included are replacement tasks for copy and javac that integrate support for preprocessing. This release adds support for Ant 1.6 antlibs, includes much more documentation, and has been reorganized to make it even easier to use. Please see http://vpp.sourceforge.net for more information, faq, and download information. didge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Future Of Turbine-JCS
OJB supports using JCS for distributed caching, but I don't know how many people actually use it (we don't). There is overlap between OJB and Turbine contributors Arrowhead ASP, a GPL ASP interpreter, ( http://www.tripi.com/arrowhead/ ) also uses JCS as I know the guy who wrote it =) OTOH I don't think he has ever submitted a patch or even feedback back to the Turbineers. I would prefer to see it split off to its own [sub]project if it has the community around it, but I cannot commit to contributing to it. -Brian On Dec 4, 2003, at 5:35 PM, Andrew C. Oliver wrote: So far it sounds to me like JCS is only used by Turbine and that only the Turbiners really care about it. Thus I don't see why it doesn't just get flattened into Turbine and just consider it one more turbine service. However, if it DOES have a community or at the very least someone who loves cares and feeds it, then commons sounds like a reasonable place to build a community. As far as oversight, who on the PMC is on this sub-sub-subproject? From a Jakarta PMC perspective, I think that we should cease to support Sub-sub-projects with the exception of commons.* -Andy * before it is mentioned, on POI we call POIFS and HSSF subprojects but they're really just components. They're called subprojects by tradition, granted it is ambiguous but I'll leave language pedantry to RMS. ;-) On 12/4/03 12:59 PM, Henri Yandell [EMAIL PROTECTED] wrote: So your preference, as the development-community of JCS, is for a top-level-jakarta project, ie) at the log4j level? If so, we can take that up with the PMC and see what views there are. As the development community, your (and James) views count a lot, though the smallness of community is the worrying thing. Hen On Thu, 4 Dec 2003, Aaron Smuts wrote: The core of JCS is ready for a release. The project is basically a hub for 4 types of plugins, or what are called auxiliaries in JCS: memory, disk, lateral distribution, and remote sever. It requires that you use a memory plugin, but the others are optional. For each type of plugin there is an efficient implementation that people are using. These include: LRU memory manager, indexed disk cache, TCp lateral distribution, and RMI remote server. There are experimental versions of each type of plugin in an experimental source directory: a b-tree disk cache, a database disk cache, a javagroups lateral, a MRU memory manager, and others. The core of JCS is then the hub and these 4 non-experimental plugins. Currently there is only one small bug in the lateral cache recovery process, that I will fix very soon. There are additional features that are mostly extensions of the plugins. I wanted to clean up the group handling features, but this is not crucial. I wanted to add run time defragmentation to the indexed disk cache. I also want to implement clustering on the remote server. Basically, this will involve hooking up remote servers via the TCP lateral cache. All that has to be done is to work out a way to prevent circular calls for there to be clustering. The client can already fail over. I'm not sure what all the levels are called, but if we put JCS at the level of log4j, I guess as a jakarta subproject, and then issue a release, we can find out what else people might want and some more people may be interested in contributing. JCS does not need an overhaul or any significant amount of work on the core features. Most conceivable future development will involve tuning, bug fixes, improving configuration, creating sample applications, and extension development. Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
