Marcus Crafter wrote:
>On Tue, Sep 24, 2002 at 03:51:46PM +0200, Leo Simons wrote:
>
>
>>However, I think it would be a shame if it means that a future
>>fortress, or "merlin's fortress" as talked about before, would
>>need to provide yet more compatibility with old materials (ie
>>with ECM *and* fortress1). I am not familiar enough with fortress
>>to make this estimate.
>>
>>
>
> I'm not familiar enough either, but I still feel that we're
> reinventing the wheel with both Fortress and Merlin continuing as
> separate containers.
>
> I know there's been progress at unifying the common ground with the
> container/ and meta/ subprojects - but I would so much rather 1
> container to work on rather than having to choose between the 2 (as is
> currently happening on cocoon-dev).
>
> Berin, why don't we just make Fortress' MetaDataContainer extend
> from Merlin's DefaultContainer and have it provide Fortress style
> semantics ?
>
This is completely achivable. The ability to plug in a custom lifestyle
manager is already in place - which would be needed to take care of the
particular semntics implied by ECM components.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
