At 10:48 19/3/01 -0800, Harmeet Bedi wrote:
>From my past experience here is what I think could help convince marketing,
>management etc
>- A stable, well defined release.
... possibly defined as a JSR ... which may or may not be occuring atm ;)
>It may not need to be the most beautiful
>or final thing, but something good enough. It would be like say Avalon x.y
>version, without alpha or beta attached.
This would be good but until someone steps up for Management interfaces I
am loathe to try to stabilize (Partially because I think Management will
help identify our weaknesses).
>- Management Interfaces. Telnet based remote interfaces may not be
>sufficient.
Definetly - but someone needs to do it and let just say it is not a high
priority on my list atm ;)
>- Class/Module reloading.
This would be a sideffect of Management interfaces I believe.
>Less important but helpful to put up.
>- A comparison with J2EE. Most Marketing guys begin with J2EE. Some story,
>white paper would provide a good perspective.
It is hard to do this. In many ways I think Avalon/Phoenix is below most
J2EE services (ie you build servlet/ejb/other containers using
Avalon/Phoenix) but then again the base framework are useful as compliments
to standard J2EE technologies (ie servlets/apps).
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
