You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gerhard Froehlich <g-...@gmx.de> on 2002/01/07 18:46:35 UTC
[proposal] some store components for the commons-sandbox
Hi,
Currently I'm working on the Cocoon store and caching. I
implemented some store components, that are maybe useful
to migrate as Jakarta commons-sandbox components.
They mainly exist of a:
1. Store -> The overall interface
2. MRUMemoryStore -> A simple MRU Memory Store class
3. JispFilesystemStore -> A jisp
(http://www.coyotegulch.com/jisp/index.html) based
Filesystem store!
4. Some helper classes (Key's, etc...)
We use this components in the Cocoon project as a fast
(memory) and slow (filesystem) storage implementation.
In the moment they are Avalon based components but I
think they could easy changed into something more
"common" ;-).
Ok, do you think this Components are a try worth to book
into the sandbox area or just a waste of time.
(Please give a clear NO if this useless or something
double or whatever!)
Thx for your time.
Gerhard
PS: I'm committer in the Jakarta Avalon project and in
the Cocoon xml-apache project.
"Hedonist for hire... no job too easy!"
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [proposal] some store components for the commons-sandbox
Posted by Kelvin Tan <ke...@relevanz.com>.
I'm not sure if anyone is aware of
http://marc.theaimsgroup.com/?l=turbine-user&m=100872531107216&w=2, but
Aaron is intending to import JCS into Jakarta as well...
Regards,
Kelvin
----- Original Message -----
From: Arron Bates <ar...@keyboardmonkey.com>
To: Jakarta Commons Developers List <co...@jakarta.apache.org>
Sent: Tuesday, January 08, 2002 9:31 AM
Subject: Re: [proposal] some store components for the commons-sandbox
>
> Paulo Gaspar wrote:
>
> >I took a look at both - Commons cache when it was proposed and
> >Cocoon's cache some weeks ago.
> >
> >Cocoon's cache seems to be lighter, simpler and easier to use.
> >
> >The current Commons cache seems to be larger with a lot more
> >features (like the ability to have distributed caching and so
> >on). Kind of an "Enterprise Solution".
> >
> >I would say they are complementary (one size does not fit all).
> >
> True.
>
> Idea. Couldn't the code base eventually evolve the heavier
> implementation so its core is lightweight and the heavy parts a wrapper
> around that? Then the same package could be used at whatever level is
> required, cache developers are focused on the single implementation and
> also have a more unified user base.
>
> Could it be workable to move Cocoon's implementation to be the heart of
> the Common's? or are they a paradigm shift apart in their workings?
>
> Just an idea.
> No holy war intended.
>
>
> Arron.
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal] some store components for the commons-sandbox
Posted by Paulo Gaspar <pa...@krankikom.de>.
> Could it be workable to move Cocoon's implementation to be the heart of
> the Common's? or are they a paradigm shift apart in their workings?
I am not 100% sure I am the right person to answer this, but to me they
still look too different.
Maybe if we put them together here synergies start developing, or maybe
the big one ends up developing a small core that competes with (and
beats out of existence) the small one... or maybe they go separate ways.
Maybe it is to soon to know that.
I rest my case. Someone else must have a better idea... pleaseeee...
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: Arron Bates [mailto:arron@keyboardmonkey.com]
> Sent: Tuesday, January 08, 2002 2:32 AM
> To: Jakarta Commons Developers List
> Subject: Re: [proposal] some store components for the commons-sandbox
>
>
>
> Paulo Gaspar wrote:
>
> >I took a look at both - Commons cache when it was proposed and
> >Cocoon's cache some weeks ago.
> >
> >Cocoon's cache seems to be lighter, simpler and easier to use.
> >
> >The current Commons cache seems to be larger with a lot more
> >features (like the ability to have distributed caching and so
> >on). Kind of an "Enterprise Solution".
> >
> >I would say they are complementary (one size does not fit all).
> >
> True.
>
> Idea. Couldn't the code base eventually evolve the heavier
> implementation so its core is lightweight and the heavy parts a wrapper
> around that? Then the same package could be used at whatever level is
> required, cache developers are focused on the single implementation and
> also have a more unified user base.
>
> Could it be workable to move Cocoon's implementation to be the heart of
> the Common's? or are they a paradigm shift apart in their workings?
>
> Just an idea.
> No holy war intended.
>
>
> Arron.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [proposal] some store components for the commons-sandbox
Posted by Arron Bates <ar...@keyboardmonkey.com>.
Paulo Gaspar wrote:
>I took a look at both - Commons cache when it was proposed and
>Cocoon's cache some weeks ago.
>
>Cocoon's cache seems to be lighter, simpler and easier to use.
>
>The current Commons cache seems to be larger with a lot more
>features (like the ability to have distributed caching and so
>on). Kind of an "Enterprise Solution".
>
>I would say they are complementary (one size does not fit all).
>
True.
Idea. Couldn't the code base eventually evolve the heavier
implementation so its core is lightweight and the heavy parts a wrapper
around that? Then the same package could be used at whatever level is
required, cache developers are focused on the single implementation and
also have a more unified user base.
Could it be workable to move Cocoon's implementation to be the heart of
the Common's? or are they a paradigm shift apart in their workings?
Just an idea.
No holy war intended.
Arron.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal] some store components for the commons-sandbox
Posted by Gerhard Froehlich <g-...@gmx.de>.
>-----Original Message-----
>From: Craig R. McClanahan [mailto:craigmcc@apache.org]
>Sent: Tuesday, January 08, 2002 9:48 PM
>To: Jakarta Commons Developers List
>Cc: paulo.gaspar@krankikom.de
>Subject: RE: [proposal] some store components for the commons-sandbox
>
>
>
>
>On Tue, 8 Jan 2002, Gerhard Froehlich wrote:
>
>> Ok, if you like them to test, then I ask for enough karma in the sandbox
>> area to commit the components.
>
>Done.
>
Thx a lot and a big _HELLO_ to everybody!
<shortbio>
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100815301815808&w=2
</shotbio>
Gerhard
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal] some store components for the commons-sandbox
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 8 Jan 2002, Gerhard Froehlich wrote:
> Ok, if you like them to test, then I ask for enough karma in the sandbox
> area to commit the components.
Done.
>
> Gerhard
>
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal] some store components for the commons-sandbox
Posted by Gerhard Froehlich <g-...@gmx.de>.
Hi,
thx for the replies (I thought this wouldn't be recognized
'cause of the heavy noise in the general list).
We (Cocoon) alway make a difference between caching and storing.
Under a Cache we do understand something like that:#
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100820114404337&w=2
(one of those excellent RT from Stefano).
The Store components are just the end point of our caching. They
are small, fast and simple designed. As I said a MRU algorithm for
Memory storing and a B-Tree (jisp) implementation for a persistent
Store.
Ok, if you like them to test, then I ask for enough karma in the sandbox
area to commit the components.
Gerhard
>-----Original Message-----
>From: Paulo Gaspar [mailto:paulo.gaspar@krankikom.de]
>Sent: Tuesday, January 08, 2002 2:25 AM
>To: Jakarta Commons Developers List
>Subject: RE: [proposal] some store components for the commons-sandbox
>
>
>I took a look at both - Commons cache when it was proposed and
>Cocoon's cache some weeks ago.
>
>Cocoon's cache seems to be lighter, simpler and easier to use.
>
>The current Commons cache seems to be larger with a lot more
>features (like the ability to have distributed caching and so
>on). Kind of an "Enterprise Solution".
>
>I would say they are complementary (one size does not fit all).
>
>
>Have fun,
>Paulo Gaspar
>
>> -----Original Message-----
>> From: Jeff Turner [mailto:jeff@socialchange.net.au]
>> Sent: Monday, January 07, 2002 11:52 PM
>> To: Jakarta Commons Developers List
>> Subject: Re: [proposal] some store components for the commons-sandbox
>>
>>
>> On Mon, Jan 07, 2002 at 06:46:35PM +0100, Gerhard Froehlich wrote:
>> > Hi,
>> > Currently I'm working on the Cocoon store and caching. I
>> > implemented some store components, that are maybe useful
>> > to migrate as Jakarta commons-sandbox components.
>> > They mainly exist of a:
>> > 1. Store -> The overall interface
>> > 2. MRUMemoryStore -> A simple MRU Memory Store class
>> > 3. JispFilesystemStore -> A jisp
>> > (http://www.coyotegulch.com/jisp/index.html) based
>> > Filesystem store!
>> > 4. Some helper classes (Key's, etc...)
>> >
>> > We use this components in the Cocoon project as a fast
>> > (memory) and slow (filesystem) storage implementation.
>> > In the moment they are Avalon based components but I
>> > think they could easy changed into something more
>> > "common" ;-).
>> >
>> > Ok, do you think this Components are a try worth to book
>> > into the sandbox area or just a waste of time.
>>
>> That would be very cool. I didn't know Cocoon's cache/store was
>> 'detachable' from the rest of Cocoon, but I'm glad it is (having once
>> had to manually rip out Cocoon 1's cache for a project;).
>>
>> Btw, there is already a cache in the sandbox, which IIRC from a
>> conversation looong ago, is already pretty mature and tested. If anyone
>> knows both codebases, it would be nice to have a comparison, for the
>> benefit of users trying to choose.
>>
>>
>> --Jeff
>>
>> > Thx for your time.
>> >
>> > Gerhard
>> >
>> > PS: I'm committer in the Jakarta Avalon project and in
>> > the Cocoon xml-apache project.
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
><ma...@jakarta.apache.org>
>For additional commands, e-mail:
><ma...@jakarta.apache.org>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal] some store components for the commons-sandbox
Posted by Paulo Gaspar <pa...@krankikom.de>.
I took a look at both - Commons cache when it was proposed and
Cocoon's cache some weeks ago.
Cocoon's cache seems to be lighter, simpler and easier to use.
The current Commons cache seems to be larger with a lot more
features (like the ability to have distributed caching and so
on). Kind of an "Enterprise Solution".
I would say they are complementary (one size does not fit all).
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: Jeff Turner [mailto:jeff@socialchange.net.au]
> Sent: Monday, January 07, 2002 11:52 PM
> To: Jakarta Commons Developers List
> Subject: Re: [proposal] some store components for the commons-sandbox
>
>
> On Mon, Jan 07, 2002 at 06:46:35PM +0100, Gerhard Froehlich wrote:
> > Hi,
> > Currently I'm working on the Cocoon store and caching. I
> > implemented some store components, that are maybe useful
> > to migrate as Jakarta commons-sandbox components.
> > They mainly exist of a:
> > 1. Store -> The overall interface
> > 2. MRUMemoryStore -> A simple MRU Memory Store class
> > 3. JispFilesystemStore -> A jisp
> > (http://www.coyotegulch.com/jisp/index.html) based
> > Filesystem store!
> > 4. Some helper classes (Key's, etc...)
> >
> > We use this components in the Cocoon project as a fast
> > (memory) and slow (filesystem) storage implementation.
> > In the moment they are Avalon based components but I
> > think they could easy changed into something more
> > "common" ;-).
> >
> > Ok, do you think this Components are a try worth to book
> > into the sandbox area or just a waste of time.
>
> That would be very cool. I didn't know Cocoon's cache/store was
> 'detachable' from the rest of Cocoon, but I'm glad it is (having once
> had to manually rip out Cocoon 1's cache for a project;).
>
> Btw, there is already a cache in the sandbox, which IIRC from a
> conversation looong ago, is already pretty mature and tested. If anyone
> knows both codebases, it would be nice to have a comparison, for the
> benefit of users trying to choose.
>
>
> --Jeff
>
> > Thx for your time.
> >
> > Gerhard
> >
> > PS: I'm committer in the Jakarta Avalon project and in
> > the Cocoon xml-apache project.
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [proposal] some store components for the commons-sandbox
Posted by Jeff Turner <je...@socialchange.net.au>.
On Mon, Jan 07, 2002 at 06:46:35PM +0100, Gerhard Froehlich wrote:
> Hi,
> Currently I'm working on the Cocoon store and caching. I
> implemented some store components, that are maybe useful
> to migrate as Jakarta commons-sandbox components.
> They mainly exist of a:
> 1. Store -> The overall interface
> 2. MRUMemoryStore -> A simple MRU Memory Store class
> 3. JispFilesystemStore -> A jisp
> (http://www.coyotegulch.com/jisp/index.html) based
> Filesystem store!
> 4. Some helper classes (Key's, etc...)
>
> We use this components in the Cocoon project as a fast
> (memory) and slow (filesystem) storage implementation.
> In the moment they are Avalon based components but I
> think they could easy changed into something more
> "common" ;-).
>
> Ok, do you think this Components are a try worth to book
> into the sandbox area or just a waste of time.
That would be very cool. I didn't know Cocoon's cache/store was
'detachable' from the rest of Cocoon, but I'm glad it is (having once
had to manually rip out Cocoon 1's cache for a project;).
Btw, there is already a cache in the sandbox, which IIRC from a
conversation looong ago, is already pretty mature and tested. If anyone
knows both codebases, it would be nice to have a comparison, for the
benefit of users trying to choose.
--Jeff
> Thx for your time.
>
> Gerhard
>
> PS: I'm committer in the Jakarta Avalon project and in
> the Cocoon xml-apache project.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>