I think the fact that Cocoon2 was build with Avalon is a great propaganda of
the deed.
> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: den 31 juli 2001 22:06
> To: [EMAIL PROTECTED]
> Subject: A couple comments from Slashdot
>
>
> It seems we may need to be less buzzward compliant on our press release:
>
> zpengo
> ------
> "The Avalon framework consists of interfaces that define
> relationships between commonly used application components,
> best-of-practice pattern enforcements, and several lightweight
> convenience implementations of the generic components."
>
> I'm sorry, could someone translate that into English?
Berin,
well, note that the quote isn't taken from the /. article, but from the
Avalon/Framework homepage at http://jakarta.apache.org/avalon/framework/.
Had zpengo bothered to read the next sentence:
"What that means is that we define the central interface Component. We also
define the relationship (contract) a component has with peers, ancestors and
children. This documentation introduces you to those patterns, interfaces
and relationships."
Maybe he would have understood it a bit better.
However, I agree that it is a lousy start and isn't exactly easy reading.
Maybe a bulleted list would be better, or splitting it into several
sentences:
"Note to the impatient: The Avalon Framework is already used in Cocoon2, an
XML publishing framework. If you are evaluating Avalon and want the
'propaganda of the deed,' check it out.
"The Avalon Framework is intended to aid the development of server
applications by providing interfaces defining common design patterns. This
means that a programmer can use tried and tested designs which makes for a
secure product, as well as an increase in code re-use.
"The Avalon Framework raises the abstraction level from Object-Oriented
Programming concept one notch to the Component-Oriented Programming model.
This enables programmers to concern themselves with assemblies of classes,
rather than the classes themselves - thus reducing the number of things the
programmer must keep in mind, and speeding up application development.
"Convenience implementations of common components are included in the
framework."
"To sum it up: The Avalon Framework provides:
- Ready-to-use design patterns.
- A higher level of abstraction than OOP.
- Implementations of common components."
> elfkicker
> ---------
> Java people get to use all the best buzzwords. That's what
> happens when APIs are edited by the marketing department.
>
> And to answer your question, no I can't.
Elfkicker is responding to the quote, which as I wrote is taken somewhat out
of context. I can't translate the little snippet either as it was presented
on /..
> NOTE:
> I checked some of zpengo's other posts and he is pretty cynical
> about everything.
>
> Elfkicker only has two responses--and the other one is pretty intelligent.
I checked them both out. As far as the Avalon posts are concerned, while
they did point out a problem, I don't think they put too much time or
research behind those two posts. Which, of course, can be caused by a total
non-interest in Avalon or server-side Java programming.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
