Niclas Hedhman wrote:
On Monday 29 December 2003 23:32, Fernando Padilla wrote:
I had another idea as well.
_I_ feel a bit "nervous" about the explicit use of the embedded case without it being properly reviewed/discussed. I _fear_ the forward-compatibility issue, where these "ad-hoc solutions" has to be supported in the future.
Can it be explicitly be marked "experimental" right away??? (Somewhere!)
I'm not fussed about the updates to fix Fernando's problem - but the general case of the event model for meta model is something is going to be an evolving thing. But this does bring up the question about status of APIs and the impact this has on committment to maintaining APIs as is. I've been thinking about this alot recently and in my own mind I see two distinct contracts. Firstly there is the block specification which *must* supported across version changes (i.e. your blocks just keep on working). Secondly there is the embedding scenario. In this area I think we should be a lot more liberal and allow development but be strict about version control, frequent releases, active development, and not get locked into a high back-end maintenance scenario.
What this translates to is high priority on backward compatability towards component authors, and high priority on evolution on the container side - which suggests that anyone doing an emabedded solution should be subscribed to the dev list and tracking development. My guess is the the numbers of component developers are multiple orders of magnitude more than embedding and kernel developers - and that's reasonable grounds focussing on the evolution priority.
Cheers, Stepehen.
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
