Return-Path: Delivered-To: apmail-jakarta-avalon-cvs-archive@apache.org Received: (qmail 57915 invoked from network); 30 Oct 2001 14:48:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Oct 2001 14:48:59 -0000 Received: (qmail 23051 invoked by uid 97); 30 Oct 2001 14:40:56 -0000 Delivered-To: qmlist-jakarta-avalon-cvs-archive@jakarta.apache.org Received: (qmail 22990 invoked by uid 97); 30 Oct 2001 14:40:55 -0000 Mailing-List: contact avalon-cvs-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon CVS List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-cvs@jakarta.apache.org Received: (qmail 22830 invoked from network); 30 Oct 2001 14:40:51 -0000 Date: 30 Oct 2001 14:31:05 -0000 Message-ID: <20011030143105.63523.qmail@icarus.apache.org> From: bloritsch@apache.org To: jakarta-avalon-cvs@apache.org Subject: cvs commit: jakarta-avalon/src/documentation/xdocs/developing conclusion.xml X-Spam-Rating: taz3.hyperreal.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N bloritsch 01/10/30 06:31:05 Modified: src/documentation/xdocs/developing conclusion.xml Log: remove tabs Revision Changes Path 1.2 +28 -28 jakarta-avalon/src/documentation/xdocs/developing/conclusion.xml Index: conclusion.xml =================================================================== RCS file: /home/cvs/jakarta-avalon/src/documentation/xdocs/developing/conclusion.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- conclusion.xml 2001/07/18 14:35:41 1.1 +++ conclusion.xml 2001/10/30 14:31:05 1.2 @@ -55,12 +55,12 @@ Designed by the Best Minds The authors of Avalon recognize that we are not the sole experts - on server side programming. We use concepts and ideas from other - people's research. We respond to feedback from our users. Avalon - is not just designed by the five developers mentioned in the - introduction—the people who came up with the concepts of Inversion - of Control, Separation of Concerns, and Component Oriented - Programming design it. + on server side programming. We use concepts and ideas from other + people's research. We respond to feedback from our users. Avalon + is not just designed by the five developers mentioned in the + introduction—the people who came up with the concepts of Inversion + of Control, Separation of Concerns, and Component Oriented + Programming design it. The beauty of Open Source projects is that the result is an @@ -77,43 +77,43 @@ Compatible License The Apache Software License (ASL) is compatible - with just about every other license known. The biggest known - exceptions are the GNU Public License (GPL) - and the Lesser GNU Public License (LGPL). The - important thing is that the ASL is friendly to corporate development, - and does not force you to release your source code if you don't want - to. It is the same license used for the Apache Software Foundation's - venerable HTTP server. + with just about every other license known. The biggest known + exceptions are the GNU Public License (GPL) + and the Lesser GNU Public License (LGPL). The + important thing is that the ASL is friendly to corporate development, + and does not force you to release your source code if you don't want + to. It is the same license used for the Apache Software Foundation's + venerable HTTP server.
Pooled Research Most of Avalon's users contribute back to the project in some way. - This spreads the cost of developing, debugging, and documenting the - framework across several users. It also means that Avalon's code - has gone through a more extensive peer review than would ever be - possible in one company. In addition, users of Avalon support - Avalon. While it is true open source projects do not typically have - a help desk or telephone support line, we do have a mailing list. - Many times your questions can be answered in less time on the list - than it would take on some support lines. + This spreads the cost of developing, debugging, and documenting the + framework across several users. It also means that Avalon's code + has gone through a more extensive peer review than would ever be + possible in one company. In addition, users of Avalon support + Avalon. While it is true open source projects do not typically have + a help desk or telephone support line, we do have a mailing list. + Many times your questions can be answered in less time on the list + than it would take on some support lines.
Simplified Analysis and Design Developing on Avalon helps the developer to get into a mindset. - That mindset focuses the efforts on how to discover Components and - Services. Since many of the details regarding the life of the - Components and Services in the system are already analyzed and - designed, the developer only has to choose which ones they need. + That mindset focuses the efforts on how to discover Components and + Services. Since many of the details regarding the life of the + Components and Services in the system are already analyzed and + designed, the developer only has to choose which ones they need. It is important to state that Avalon development does not replace - traditional Object Oriented Analysis and Design, but enhances it. - You are still using the same techniques you did before, only now - you have a tool set you can use to achieve your design faster. + traditional Object Oriented Analysis and Design, but enhances it. + You are still using the same techniques you did before, only now + you have a tool set you can use to achieve your design faster.
-- To unsubscribe, e-mail: For additional commands, e-mail: