cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Froehlich" <g-froehl...@gmx.de>
Subject RE: Release Plans (was RE: New Components From Avalon Scratchpad)
Date Sun, 13 Jan 2002 16:30:50 GMT
Berin,

>From: Berin Loritsch [mailto:bloritsch@apache.org]
>
>Gerhard Froehlich wrote:
>
>>>From: Berin Loritsch [mailto:bloritsch@apache.org]
>>>
>>>Gerhard Froehlich wrote:
>>>
>>>
>>>>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>>>>>
>>>>>Hi Team,
>>>>>
>>>>>it seems that it is time to think of some release plans.
>>>>>Thanks to Giacomo we have the new directory structure in our CVS
>>>>>and thanks to all of us we have a working HEAD cvs, so we can
>>>>>deprecate the 2.0 branch making the development much easier for
>>>>>all of us.
>>>>>
>>>>>So, these questions need to be answered:
>>>>>a) What is the version of the next release?
>>>>>
>>>>>b) Are there open problems/bugs which must be fixed?
>>>>>
>>>>>c) Are there outstanding issues which should go into a next release?
>>>>>
>>>>>
>>>>I would like to put the new jisp store and the refactored MRUMemoryStore
>>>>in the new release. I believe that will be a real improvement! Do you tested
>>>>this component? You find it in the scratchpad.
>>>>
>>>
>>>Before you incorporate the cache changes, I would like to see one configuration
>>>for the whole cache.  The Cache Janitor is strictly used for the cache, and
>>>can be started and stopped by the MRUMemoryStore directly.
>>>
>> 
>> You mean putting all under one <store/> configuration? Under the point that
all
>> is "Store", then I like it (+1).
>
>
>Exactly!

Berin, I did some thoughts about that issue. From SoC point of view this will break
the Avalon SoC design. You are right all this components are under the Store package.
But each of them are standalone components (90%), with their own responsibilities.
I don't want to wire this components to much together.

Hmm maybe I'm wrong here, but how would you solve this?
1. each Store component can somehow access the <store/> section in the cocoon.xconf
file. But I don't have a idea how.
2. the MRUMemoryStore configures the rest of the Store compents via public setter,
getter methods.

What do you think?

  Gerhard

"God put me on this Earth to accomplish a certain number of things. 
Right now, I am so far behind I shall never die."


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message