After David Taylor's mail about his setup problems I'd like to disable
(deprecate) public access to the internal ResourceLocator and have the
Configuration subclass act strictly as a facade, with individual
capabilities. Exposing the internal behaviour of such a 'fat' utility
object always kind of bugged me and Dave's attempts show that when there's
a bunch of public methods, people will call them, trying to 'fix' things.
A good API should prevent that, IMHO.
Holger
This archive was generated by hypermail 2.0.0 : Sun May 11 2003 - 11:50:41 EDT