> From: Leo Simons [mailto:[EMAIL PROTECTED]] > > On Tue, 2002-08-27 at 18:04, Berin Loritsch wrote: > > I would like to propose a minimum set of attributes that all > > containers need to support, which will provide some > guarantees for the > > components that need them. > > +1. IOW, this is an extension of the contract for the Context > interface. > "If a container provides feature X, it must do so using the > following key and the following value type". Right?
Right. > > So far, I only have three that would fit the bill: > > > > 1) "context:dir" A java.io.File representing the context directory > > available > > to the component. Sort of a "home" directory. > > > > 2) "context:scratch" A java.io.File representing the > context directory > > that the component can use as a hash area--nothing permanent > > guaranteed, > > but useful for dynamic compilation, cache entries, etc. > > > > 3) "context:classloader" A java.lang.ClassLoader that the > component can > > use to create objects or child components with. > > > > > > The names are of course up for debate, but the concepts are fairly > > constant. > > +1. For naming I like postfixing dirs with .dir (I do it in ant > buildfiles all the time, anyway =). > > I'd say > > avalon:context.home.dir > avalon:context.scratch.dir > avalon:context.classloader > > ^^^ --> to be real clear about the "level of endorsement" here. > > > Thoughts? > > yup. I suggest stuff like this will be specified in the > future in javadocs for the framework package and in an xdoc > for the framework reference, and until things finalize inside > the containerkit/meta package. Yep. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
