4 Replies Latest reply on Aug 2, 2006 4:59 AM by Galder Zamarreño

    Protected fields in TreeCache

    Brian Stansberry Master

      As part of the API cleanup for 2.0, what do people think about changing all the protected fields in TreeCache to private, or, if needed, package-protected? A protected field is really part of a class' public API. Since we're going to the effort of locking down all the API's, this seems like a good thing to lock down as well.

      If any of these fields really need to be exposed to subclasses, we can do it through a protected setter/getter, which IMHO is a more controlled way of exposing something as part of the public API.

      I realize we're doing things like using Cache and CacheSPI to isolate the "user API" from the internal one, but I think its also a good practice to limit the public API of the internal classes as much as possible.