Thank you, Berin. So, the two interfaces are just two different ways of configuring an Avalon-aware object. One can live without the other.
On Wed, 19 Sep 2001 08:38:18 -0400 Berin Loritsch wrote: > Jeremias Maerki wrote: > > > > Hi there > > > > After looking through the documentation and the mailing list archives I > > still don't know why there are two interfaces Configurable and > > Parameterizable. I've seen some mails from April when Parameterizable > > was introduced, but that didn't help. Also, the API docs simply state > > that the two interfaces are incompatible. I currently believe > > Parameterizable isn't needed, because I can do all > > configuration/parameterization I need using Configurable. > > True. The difference is when all you need is a flat configuration scheme > as opposed to a hierarchical one. > > Parameters is much like Properties with the exception of type safety built > in. It is a flat configuration scheme--easily derived from a heirarchical > one. > > Configuration is for when your Configuration elements need to be expressed > in a more rich manner. It allows you to group sub configurations together > very easily. > > > As far as the overall weight of the objects, the Parameters object is lighter > than the Configuration object. Cheers, Jeremias M�rki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
