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.42.2.1 -r1.42.2.2 --- openacs-4/packages/acs-core-docs/www/apm-design.html 2 Mar 2019 19:30:04 -0000 1.42.2.1 +++ openacs-4/packages/acs-core-docs/www/apm-design.html 3 Sep 2021 09:14:47 -0000 1.42.2.2 @@ -7,7 +7,7 @@ apm-install-procs.tcl (Supports installation of packages)

  • 30-apm-load-procs.tcl (Bootstraps APM for server startup)

  • apm-admin-procs.tcl (Supports APM UI)

  • PL/SQL file

  • Introduction

    -In general terms, a package is a unit of software that +In general, a package is a unit of software that serves a single well-defined purpose. That purpose may be to provide a service directly to one or more classes of end-user, (e.g., discussion forums and file storage for community members, user profiling tools for the site @@ -509,7 +509,7 @@ This approach has certain advantages, such as centralization, but splitting this information into several files allows for flexible extensions to the APM architecture over time.

    APM packages currently lack provisions to verify security information. -There are plans to add MD5 time stamps and PGP signatures to packages to +There are plans to add MD5 timestamps and PGP signatures to packages to enable secure authentication of packages. These steps are necessary for APM to be usable as a scalable method to distribute packages on multiple repositories worldwide.

    Another anticipated change is to split the APM UI into separate systems