Index: openacs-4/packages/acs-core-docs/www/apm-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/apm-design.html,v diff -u -r1.13 -r1.14 --- openacs-4/packages/acs-core-docs/www/apm-design.html 21 Oct 2003 10:04:47 -0000 1.13 +++ openacs-4/packages/acs-core-docs/www/apm-design.html 28 Oct 2003 22:07:33 -0000 1.14 @@ -1,4 +1,4 @@ -OpenACS 5.0.0a1 Package Manager Design

OpenACS 5.0.0a1 Package Manager Design

+OpenACS 5.0.0a1 Package Manager Design

OpenACS 5.0.0a1 Package Manager Design

by Bryan Quinn
OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. @@ -24,7 +24,7 @@

  • OpenACS Services: the aforementioned building blocks. Examples of services include the OpenACS Content Repository, the OpenACS Templating -System, and the OpenACS Kernel, which includes +System, and the OpenACS Kernel, which includes APM.

  • An installation of the OpenACS includes the OpenACS Kernel, some services that extend the kernel's functionality, and some applications intended for end-users. Packages function as individual pieces of subsites. A subsite can contain multiple @@ -88,7 +88,7 @@ packages for other ACS users to download and install.

    For a simple illustration of the difference between ACS without APM (pre-3.3) and ACS with APM (3.3 and beyond), consider a hypothetical ACS installation that uses only two of the thirty-odd modules available circa ACS -3.2 (say, bboard and e-commerce):

    APM itself is part of a package, the OpenACS Kernel, an OpenACS +3.2 (say, bboard and e-commerce):

    APM itself is part of a package, the OpenACS Kernel, an OpenACS service that is the only mandatory component of an OpenACS installation.

    Competitive Analysis

    The OpenACS is a platform for web-based application software, and any software platform has the potential to develop problems like those described above. Fortunately, there are many precedents for systematic solutions,