From: Scott M S. <sco...@jb...> - 2005-11-19 20:13:19
|
Adrian Brock wrote: > On Sat, 2005-11-19 at 14:17, Scott M Stark wrote: >> The real question/point of this message is, what is the next step in >> runtime metadata abstraction that allows us to move both 4.0.x and 5.0.x >> forward with support for these features such that is not a support and >> maintence nightmare as the mc comes online. > > My question would be where does the old model leak into the > public api/spi such that it is difficult to change? > > I think my feelings are well known? > With people exposing all sorts of implementation and integration details > making things less easy to change. Even across modules in the > same release, let alone modules across different versions. This is the point. First, what basis for a unified view of the metadata and management exists today such that an abstraction can be put in place for aspects and other services that should be separable from implementation details. Given that, how can this be introduced into the legacy server. |