Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3AB765E2.A90CDAF1@apache.org>
Date: Tue, 20 Mar 2001 09:14:58 -0500
From: Berin Loritsch <bloritsch@apache.org>
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Adopt Modifiable?
References: <3.0.6.32.20010320192915.00a9b170@alphalink.com.au>
 <3.0.6.32.20010321010456.00aed100@alphalink.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Donald wrote:
> 
> At 08:43  20/3/01 -0500, Berin Loritsch wrote:
> >Not sure.  Can't there be other types of Components/Servers that use
> >Modifiable?  It would help with my DataXfer project where I need to
> >check if a Job has been run yet or not.  I think it was moved there
> >with that thought in mind.
> 
> It is good for caching scenarios. However Avalon has been receiving a lot
> of flack recently because it has a lot of untested bits. My philosophy has
> been if class X is not used by 2 or more projects then it probably is not
> general enough and should be stored with the project. If we find that X is
> useful and tested in multiple domains then we can move it back into Avalon.
> Note that at that stage it would presumably tested and stable.

Well the Modifiable Interface is pretty well tested, and useful in more
than one project--my proprietary one and Cocoon.  Also in a project I am
starting for an XForms implementation designed to plug into Cocoon and
using Avalon.

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