Index: openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl,v diff -u -N -r1.93.2.18 -r1.93.2.19 --- openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl 15 Jun 2020 14:29:22 -0000 1.93.2.18 +++ openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl 2 Jul 2020 08:31:17 -0000 1.93.2.19 @@ -492,7 +492,7 @@ if {$::xo::rss} { # # The following code works just for Linux, since it depends on - # the /proc file system and the order of values in the resulting + # the /proc filesystem and the order of values in the resulting # line. # if {[file readable /proc/[pid]/statm]} { Index: openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl,v diff -u -N -r1.148.2.20 -r1.148.2.21 --- openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl 11 May 2020 19:14:53 -0000 1.148.2.20 +++ openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl 2 Jul 2020 08:31:17 -0000 1.148.2.21 @@ -22,7 +22,7 @@ # database connection is configured in an object ::xo::dc (for # database context) quite similar to ::xo::cc (the default # connection context). In general ::xo::dc can be reconfigured at - # runtime, and multiple database context can be established, + # run time, and multiple database context can be established, # although there is no high-level support to connect to multiple # different OpenACS databases at the same time. # @@ -1201,8 +1201,8 @@ @return class name of the created XOTcl class } { - # some table_names and id_columns in acs_object_types are unfortunately upper case, - # so we have to convert to lower case here.... + # some table_names and id_columns in acs_object_types are unfortunately uppercase, + # so we have to convert to lowercase here.... ::xo::dc 1row fetch_class { select object_type, supertype, pretty_name, lower(id_column) as id_column, lower(table_name) as table_name from acs_object_types where object_type = :object_type @@ -2816,7 +2816,7 @@ ############## ad_proc tcl_date {timestamp tz_var {secfrac_var ""}} { - Convert the time stamp (coming from the database) into a format, which + Convert the timestamp (coming from the database) into a format, which can be passed to Tcl's "clock scan". } { upvar $tz_var tz Index: openacs-4/packages/xotcl-core/tcl/bgdelivery-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/bgdelivery-procs.tcl,v diff -u -N -r1.68.2.11 -r1.68.2.12 --- openacs-4/packages/xotcl-core/tcl/bgdelivery-procs.tcl 17 Apr 2020 17:28:40 -0000 1.68.2.11 +++ openacs-4/packages/xotcl-core/tcl/bgdelivery-procs.tcl 2 Jul 2020 08:31:17 -0000 1.68.2.12 @@ -304,7 +304,7 @@ Subscriber instproc close {} { set channel [:channel] # - # It is important to make the channel non-blocking for the close, + # It is important to make the channel nonblocking for the close, # since otherwise the close operation might block and bring all of # bgdelivery to a halt. # @@ -572,7 +572,7 @@ # we have to obtain the size from the file; unfortunately, this # requires a duplicate open+close of the h264 stream. If the # application is performance sensitive, one might consider to use - # the possibly incorrect size form the file system instead (works + # the possibly incorrect size form the filesystem instead (works # perfectly for e.g. flowplayer) if {[catch {set handle [h264open $filename $query]} errorMsg]} { ns_log error "h264: error opening h264 channel for $filename $query: $errorMsg" @@ -605,7 +605,7 @@ if {$from eq ""} { # The last $to bytes, $to must be specified; 'to' is # differently interpreted as in the case, where from is - # non-empty + # nonempty set from [expr {$size - $to}] } else { if {$to eq ""} {set to [expr {$size-1}]} Index: openacs-4/packages/xotcl-core/tcl/generic-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/generic-procs.tcl,v diff -u -N -r1.112.2.4 -r1.112.2.5 --- openacs-4/packages/xotcl-core/tcl/generic-procs.tcl 9 Aug 2019 19:45:14 -0000 1.112.2.4 +++ openacs-4/packages/xotcl-core/tcl/generic-procs.tcl 2 Jul 2020 08:31:17 -0000 1.112.2.5 @@ -108,7 +108,7 @@ ${:data} rename -old_name $old_name -new_name $new_name # # Check, whether we have to change the redirect url due to - # renaming. When the method returns non-empty use this value. + # renaming. When the method returns nonempty use this value. # set url [${:data} changed_redirect_url] if {$url ne ""} { Index: openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl,v diff -u -N -r1.40.2.4 -r1.40.2.5 --- openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl 9 Aug 2019 19:45:14 -0000 1.40.2.4 +++ openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl 2 Jul 2020 08:31:17 -0000 1.40.2.5 @@ -26,7 +26,7 @@ # Defined classes # 1) HttpCore (common base class) # 2) HttpRequest (for blocking requests + timeout support) - # 3) AsyncHttpRequest (for non-blocking requests + timeout support) + # 3) AsyncHttpRequest (for nonblocking requests + timeout support) # 4) HttpRequestTrace (mixin class) # 5) Tls (mixin class, applicable to various protocols) # @@ -197,7 +197,7 @@ set trl [expr {[string match "text/*" $content_type] ? $text_translation : "binary"}] # - # 3. In the following, I realise a IANA/MIME charset resolution + # 3. In the following, I realize a IANA/MIME charset resolution # scheme which is compliant with RFC 3023 which deals with # treating XML media types properly. # @@ -540,7 +540,7 @@ } # - # Asynchronous (non-blocking) requests + # Asynchronous (nonblocking) requests # Class create AsyncHttpRequest -superclass HttpCore -slots { Index: openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl,v diff -u -N -r1.67.2.22 -r1.67.2.23 --- openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl 1 Jul 2020 14:35:28 -0000 1.67.2.22 +++ openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl 2 Jul 2020 08:31:17 -0000 1.67.2.23 @@ -522,7 +522,10 @@ @param report Report type of the instance. This could e.g. be hours and minutes @param timeoutMS How often are the statistics for this report computed - @param stats stats keeps nr_stats_elements highest values with time stamp. These hold a list of lists of the actual stats in the form {time value}. Time is given like "Thu Sep 13 09:17:30 CEST 2007". This is used for displaying the Max values + @param stats stats keeps nr_stats_elements highest values with timestamp. + These hold a list of lists of the actual stats in the form {time value}. + Time is given like "Thu Sep 13 09:17:30 CEST 2007". + This is used for displaying the maximum values @param trend trend keeps nr_trend_elements most recent values. This is used for displaying the graphics @param c counter @param logging If set to 1 the instance current value is logged to the counter.log file @@ -567,7 +570,7 @@ set :trend [lrange ${:trend} $lt-${:nr_trend_elements} end] } # - # stats keeps nr_stats_elements highest values with time stamp + # stats keeps nr_stats_elements highest values with timestamp # lappend :stats [list $timestamp $n] set :stats [lrange [lsort -real -decreasing -index 1 ${:stats}] 0 ${:nr_stats_elements}-1] @@ -1204,7 +1207,7 @@ } # - # The array "urls" keeps triples of time stamps, URLs and peer + # The array "urls" keeps triples of timestamps, URLs and peer # addresses per user. # lappend :urls($key) [list ${:point_in_time} $url $pa] @@ -1454,7 +1457,7 @@ } # - # The remainder are primarily runtime statistics + # The remainder are primarily run time statistics # if {[$o array exists $var]} { lappend cmds [list $o array set $var [$o array get $var]] Index: openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml,v diff -u -N -r1.24 -r1.24.2.1 --- openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 24 Dec 2017 13:15:07 -0000 1.24 +++ openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 2 Jul 2020 08:39:25 -0000 1.24.2.1 @@ -317,7 +317,7 @@ Identify any new locales that have been created. For each new locale, check the parameters, especially that the locale is in the format [two-letter code for - language, lower-case]_[TWO-LETTER CODE FOR COUNTRY, + language, lowercase]_[TWO-LETTER CODE FOR COUNTRY, UPPER-CASE], and create a sql command. A example sql command for creating a locale is: insert into ad_locales @@ -326,7 +326,7 @@ values ('fa_IR', 'Farsi (IR)', 'fa', 'IR', 'FARSI', 'IRAN', 'AL24UTFFSS', 'windows-1256', 't', 'f'); Put this command into the following four files. For the - upgrade files, the correct file name will depend on the + upgrade files, the correct filename will depend on the exact version. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml,v diff -u -N -r1.17.2.2 -r1.17.2.3 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 1 Nov 2019 13:16:18 -0000 1.17.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 2 Jul 2020 08:39:25 -0000 1.17.2.3 @@ -185,15 +185,15 @@ cannot change the actual text of the query, only the literal values in the placeholders. The database API makes bind variables easy to use by hooking them smoothly into the Tcl - runtime so you simply provide :tclvar and the value of $tclvar + run time so you simply provide :tclvar and the value of $tclvar is sent to the backend to actually execute the query. The database API parses the query and pulls out all the bind variable specifications and replaces them with generic placeholders. It then automatically pulls the values of the named Tcl vars out of the - runtime environment of the script, and passes them to the database. + run time environment of the script, and passes them to the database. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml,v diff -u -N -r1.28.2.1 -r1.28.2.2 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml 10 Mar 2019 21:44:57 -0000 1.28.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml 2 Jul 2020 08:39:25 -0000 1.28.2.2 @@ -115,7 +115,7 @@ keys and localized ADP files. For ADP pages which are mostly code, replacing the message text with message key placeholders is simpler. This approach also allows new translation in the - database, without affecting the file system. For ADP pages + database, without affecting the filesystem. For ADP pages which are static and mostly text, it may be easier to create a new ADP page for each language. In this case, the pages are distinguished by a file naming convention. @@ -129,7 +129,7 @@ Separate Templates for each Locale - If the request processor finds a file named filename.locale.adp, where locale matches the user's locale, it will process that file instead of filename.adp. For example, for a user with locale tl_PH, the file index.tl_PH.adp, if found, will be used instead of index.adp. The locale-specific file should thus contain text in the language appropriate for that locale. The code in the page, however, should still be in English. Message keys are processed normally. + If the request processor finds a filenamed filename.locale.adp, where locale matches the user's locale, it will process that file instead of filename.adp. For example, for a user with locale tl_PH, the file index.tl_PH.adp, if found, will be used instead of index.adp. The locale-specific file should thus contain text in the language appropriate for that locale. The code in the page, however, should still be in English. Message keys are processed normally. Message Catalogs @@ -228,7 +228,7 @@ - Static key lookup with non-default locale: [lang::message::lookup $locale package_key.message_key] - The message key and package key used here must be string literals, they can't result from variable evaluation. + Static key lookup with nondefault locale: [lang::message::lookup $locale package_key.message_key] - The message key and package key used here must be string literals, they can't result from variable evaluation. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml,v diff -u -N -r1.13 -r1.13.2.1 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml 22 Apr 2018 19:24:37 -0000 1.13 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml 2 Jul 2020 08:39:25 -0000 1.13.2.1 @@ -18,7 +18,7 @@ OpenACS. OpenACS packages are installed and maintained with the OpenACS Package Manager (APM) which is part of the acs-admin package. This document presents reasons for packaging software, - conventions for the file system and naming that must be + conventions for the filesystem and naming that must be followed, and step by step instructions for creating a new package for the "Notes" example package. @@ -65,7 +65,7 @@ logic, administration pages and user pages in a single part of the file tree. This means developers can track down everything that is related to a particular - package without hunting all over the file system. Encapsulating + package without hunting all over the filesystem. Encapsulating everything about a package in one place also makes it much easier to distribute packages independently from the OpenACS Core. @@ -463,8 +463,7 @@ This is a short text string that should uniquely name your package to distinguish it from all the others. It is used as a database key to - keep track of the package and as the name of the directory in the file - system where all the files related to your package will live. Example + keep track of the package and as the name of the directory in the filesystem where all the files related to your package will live. Example package keys in the current system include: forums, acs-kernel and so on. For the example application, we will use the package key notes. @@ -577,7 +576,7 @@ file information", then the "Scan the packages/notes directory for additional files in this package" link on that page to scan - the file system for new files. This will bring you do a page + the filesystem for new files. This will bring you do a page that lists all the files you just added and lets you add them to the notes package. @@ -650,7 +649,7 @@ In OpenACS &majorversion;, administrators can define an arbitrary mapping between the - URLs the user types and the actual file in the file system that is + URLs the user types and the actual file in the filesystem that is served. This mapping is called the site map and entries in the site map are called site nodes. Each site node maps a URL to an OpenACS object. Since package instances are objects, the site map allows Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml,v diff -u -N -r1.10 -r1.10.2.1 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml 24 Dec 2017 13:15:07 -0000 1.10 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml 2 Jul 2020 08:39:25 -0000 1.10.2.1 @@ -895,7 +895,7 @@ Read acs_rels: right-side is a - subset of left-side, ie + subset of left-side, i.e. object2 is a part of object1. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml,v diff -u -N -r1.18.2.1 -r1.18.2.2 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml 22 Nov 2019 16:30:46 -0000 1.18.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml 2 Jul 2020 08:39:25 -0000 1.18.2.2 @@ -213,7 +213,7 @@ Explicitly defining permissions to every object individually would become very tedious. -OpenACS provides a object contexts as a means for controlling permissions of a large group +OpenACS provides an object contexts as a means for controlling permissions of a large group of objects at the same time. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/subsites.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/subsites.xml,v diff -u -N -r1.10.2.1 -r1.10.2.2 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/subsites.xml 27 Jun 2019 18:15:11 -0000 1.10.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/subsites.xml 2 Jul 2020 08:39:25 -0000 1.10.2.2 @@ -63,7 +63,7 @@ application. -The RP asks the package manager where in the file system the Notes +The RP asks the package manager where in the filesystem the Notes package lives. In the standard case, this would be ROOT/packages/notes. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-debug.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-debug.xml,v diff -u -N -r1.15 -r1.15.2.1 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-debug.xml 18 Jun 2018 07:28:49 -0000 1.15 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-debug.xml 2 Jul 2020 08:39:25 -0000 1.15.2.1 @@ -100,7 +100,7 @@ Automated tests It seems to me that a lot of people have been asking for some guidelines on how to write automated tests. I've done several tests by now and have found the process to be extremely easy and useful. It's a joy to work with automated testing once you get the hang of it. Create the directory that will contain the test - script and edit the script file. The directory location and file name are standards which are recognized by the automated testing package: + script and edit the script file. The directory location and filename are standards which are recognized by the automated testing package: [$OPENACS_SERVICE_NAME www]$ mkdir /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/test [$OPENACS_SERVICE_NAME www]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/test [$OPENACS_SERVICE_NAME test]$ emacs myfirstpackages-procs.tcl Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml,v diff -u -N -r1.7.2.1 -r1.7.2.2 --- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml 9 Aug 2019 20:04:23 -0000 1.7.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml 2 Jul 2020 08:39:25 -0000 1.7.2.2 @@ -197,7 +197,7 @@ Although in theory coding comes after design, which comes after requirements, we do not, and perhaps should not, always follow such a - rigid process (a.k.a. the waterfall lifecycle). Often, there is a + rigid process (aka the waterfall lifecycle). Often, there is a pre-existing system or prototype first, and thus you may want to write some thoughts on implementation, for aiding and guiding yourself or other programmers. Index: openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml,v diff -u -N -r1.39.2.2 -r1.39.2.3 --- openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml 22 Nov 2019 16:30:46 -0000 1.39.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml 2 Jul 2020 08:39:25 -0000 1.39.2.3 @@ -768,7 +768,7 @@ NsShutdownWithNonZeroExitCode: tell NaviServer to return with a - non-zero return code to cause restart (important under windows) + nonzero return code to cause restart (important under windows) LogIncludeUserId: include user_id in access log @@ -1288,7 +1288,7 @@ Added ability to save data sent by - ns_return in files on the file system. This can be used to + ns_return in files on the filesystem. This can be used to validate HTML content also for password protected pages (controlled via package parameter "TclTraceSaveNsReturn" in the acs-tcl package parameters) Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml,v diff -u -N -r1.16.2.1 -r1.16.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 9 Aug 2019 20:04:23 -0000 1.16.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 2 Jul 2020 08:39:25 -0000 1.16.2.2 @@ -11,7 +11,7 @@ by Joel Aufrecht - In this chapter, Configuring refers to making changes to a new OpenACS site through the web interface. In crude terms, these changes happen in the database, and are upgrade-safe. Customizing refers to changes that touch the file system, and require some planning if easy upgradability is to be maintained. + In this chapter, Configuring refers to making changes to a new OpenACS site through the web interface. In crude terms, these changes happen in the database, and are upgrade-safe. Customizing refers to changes that touch the filesystem, and require some planning if easy upgradability is to be maintained. Installing OpenACS packages Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml,v diff -u -N -r1.35.2.1 -r1.35.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 5 Oct 2019 13:43:47 -0000 1.35.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 2 Jul 2020 08:39:25 -0000 1.35.2.2 @@ -339,7 +339,7 @@ to different values. - Services on different host names + Services on different hostnames For example, suppose you want to support http://service0.com and http://bar.com on the same @@ -351,8 +351,7 @@ - If you want to install two services with different host - names sharing the same ip, you'll need nsvhr to redirect requests + If you want to install two services with different hostnames sharing the same ip, you'll need nsvhr to redirect requests based on the contents of the tcp headers. See AOLserver Virtual Hosting with TCP by markd. @@ -492,7 +491,7 @@ Method 2: A/B Deployment The approach taken in this section is to always create a new service with the desired changes, running in parallel with the existing site. This guarantees control, at least at the final step of the process: you know what changes you are about to make because you can see them directly. It does not, by itself, guarantee the entire control chain. You need additional measures to make sure that the change you are making is exactly and completely the change you intended to make and tested previously, and nothing more. Those additional measures typically take the form of source control tags and system version numbers. The parallel-server approach also guarantees rollback because the original working service is not touched; it is merely set aside. - This approach can has limitations. If the database or file system regularly receiving new data, you must interrupt this function or risk losing data in the shuffle. It also requires extra steps if the database will be affected. + This approach can has limitations. If the database or filesystem regularly receiving new data, you must interrupt this function or risk losing data in the shuffle. It also requires extra steps if the database will be affected. Simple A/B Deployment: Database is not changed
@@ -688,7 +687,7 @@ users into .LRN) - Is the file system out of space? Is the machine swapping to disk constantly? + Is the filesystem out of space? Is the machine swapping to disk constantly? Isolating and solving database problems. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml,v diff -u -N -r1.33 -r1.33.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 30 Sep 2018 15:53:28 -0000 1.33 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 2 Jul 2020 08:39:25 -0000 1.33.2.1 @@ -72,7 +72,7 @@ - Set up the file system for one or more OpenACS Sites + Set up the filesystem for one or more OpenACS Sites For Linux Standard Base compliance and ease of backup, all of the files in each OpenACS site are stored in a subdirectory of Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml,v diff -u -N -r1.22 -r1.22.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 7 Aug 2017 23:47:55 -0000 1.22 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 2 Jul 2020 08:39:25 -0000 1.22.2.1 @@ -255,7 +255,7 @@ Setup the installation location for Oracle. While Oracle can - reside in a variety of places in the file system, OpenACS has + reside in a variety of places in the filesystem, OpenACS has adopted /ora8 as the base directory. @@ -1140,7 +1140,7 @@ Congratulations, you have just installed Oracle 8.1.7 Server! However, you still need to create a database which can take about an - hour of non-interactive time, so don't quit yet. + hour of noninteractive time, so don't quit yet. @@ -1304,7 +1304,7 @@ Click the "Save" button. Oracle will automatically save it to the correct - directory and with the correct file name. This will likely be + directory and with the correct filename. This will likely be /ora8/m01/app/oracle/product/8.1.7/assistants/dbca/jlib/sqlora8.sh Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml,v diff -u -N -r1.37.2.1 -r1.37.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 5 Oct 2019 13:43:47 -0000 1.37.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 2 Jul 2020 08:39:25 -0000 1.37.2.2 @@ -236,7 +236,7 @@ ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail Configure qmail - specifically, run the config script to set up files in /var/qmail/control specifying the computer's identity and which addresses it should accept mail for. This command will automatically set up qmail correctly if you have correctly set a valid host nome. If not, you'll want to read /var/qmail/doc/INSTALL.ctl to find out how to configure qmail. [root qmail-1.03]# ./config-fast yourserver.test -Your fully qualified host name is yourserver.test. +Your fully qualified hostname is yourserver.test. Putting yourserver.test into control/me... Putting yourserver.test into control/defaultdomain... Putting yourserver.test into control/plusdomain... @@ -695,7 +695,7 @@ Configure ns_ldap for use with LDAP bind - LDAP authentication usually is done by trying to bind (a.k.a. login) a user with the LDAP server. The password of the user is not stored in any field of the LDAP server, but kept internally. The latest version of ns_ldap supports this method with the ns_ldap bind command. All you have to do to enable this is to configure auth_ldap to make use of the BIND authentication instead. Alternatively you can write a small script on how to calculate the username out of the given input (e.g. if the OpenACS username is malte.fb03.tu, the LDAP request can be translated into "ou=malte,ou=fb03,o=tu" (this example is encoded in auth_ldap and you just have to comment it out to make use of it). + LDAP authentication usually is done by trying to bind (aka login) a user with the LDAP server. The password of the user is not stored in any field of the LDAP server, but kept internally. The latest version of ns_ldap supports this method with the ns_ldap bind command. All you have to do to enable this is to configure auth_ldap to make use of the BIND authentication instead. Alternatively you can write a small script on how to calculate the username out of the given input (e.g. if the OpenACS username is malte.fb03.tu, the LDAP request can be translated into "ou=malte,ou=fb03,o=tu" (this example is encoded in auth_ldap and you just have to comment it out to make use of it). Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml,v diff -u -N -r1.18 -r1.18.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml 7 Aug 2017 23:47:55 -0000 1.18 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml 2 Jul 2020 08:39:25 -0000 1.18.2.1 @@ -97,7 +97,7 @@ database to a file within the file tree. Then, you back up the file tree. All of the information needed to rebuild the site, including the AOLserver config files, is then in tree for regular - file system backup. + filesystem backup. @@ -210,7 +210,7 @@ - Back up the file system + Back up the filesystem Back up all of the files in the service, including the database backup file but excluding the auto-generated supervise directory, which is @@ -330,7 +330,7 @@ CREATE USER [postgres ~]$ exit - Because of a bug in Postgres backup-recovery, database objects are not guaranteed to be created in the right order. In practice, running the OpenACS initialization script is always sufficient to create any out-of-order database objects. Next, restore the database from the dump file. The restoration will show some error messages at the beginning for objects that were pre-created from the OpenACS initialization script, which can be ignored. + Because of a bug in Postgres backup-recovery, database objects are not guaranteed to be created in the right order. In practice, running the OpenACS initialization script is always sufficient to create any out-of-order database objects. Next, restore the database from the dump file. The restoration will show some error messages at the beginning for objects that were precreated from the OpenACS initialization script, which can be ignored. [root root]# su - $OPENACS_SERVICE_NAME [$OPENACS_SERVICE_NAME ~]$ createdb $OPENACS_SERVICE_NAME Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/red-hat.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/red-hat.xml,v diff -u -N -r1.11.2.1 -r1.11.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/red-hat.xml 9 Aug 2019 20:04:23 -0000 1.11.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/red-hat.xml 2 Jul 2020 08:39:25 -0000 1.11.2.2 @@ -136,8 +136,7 @@ guess. Click Edit, uncheck Configure using DHCP and type in your IP and netmask. Click Ok. - Type in your host -name, gateway, and DNS server(s). Then click Next. + Type in your hostname, gateway, and DNS server(s). Then click Next. We're going to use the firewall template for high security, meaning that we'll block almost all incoming traffic. Then we'll add a few holes to the firewall for services which we need and @@ -158,7 +157,7 @@ Select any additional languages you want the computer to support and then click Next - Choose your time zone and click Next. + Choose your timezone and click Next. Type in a root password, twice. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/software.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/software.xml,v diff -u -N -r1.29 -r1.29.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/software.xml 4 Jul 2018 10:20:42 -0000 1.29 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/software.xml 2 Jul 2020 08:39:25 -0000 1.29.2.1 @@ -329,7 +329,7 @@ Web Server The web server handles incoming HTTP requests, provides - a runtime environment for OpenACS's Tcl code, connects to the + a run time environment for OpenACS's Tcl code, connects to the database, sends out HTTP responses, and logs requests and errors. OpenACS uses AOLserver; some people have had success running Apache with mod_nsd. @@ -475,7 +475,7 @@ Database - The data on your site (for example, user names and passwords, + The data on your site (for example, usernames and passwords, calendar entries, and notes) is stored in the database. OpenACS separates the database with an abstraction layer, which means that several different databases all function Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml,v diff -u -N -r1.44 -r1.44.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 27 Mar 2018 12:22:17 -0000 1.44 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 2 Jul 2020 08:39:25 -0000 1.44.2.1 @@ -97,7 +97,7 @@ Make a Backup - Back up the database and file system (see ). + Back up the database and filesystem (see ). @@ -114,7 +114,7 @@ - Upgrade the file system + Upgrade the filesystem @@ -188,11 +188,11 @@ - Back up the database and file system. + Back up the database and filesystem. - Upgrade the file system for packages/acs-kernel + Upgrade the filesystem for packages/acs-kernel @@ -304,12 +304,12 @@ - Upgrade the file system for all packages in use + Upgrade the filesystem for all packages in use - Go to /acs-admin/install/ and click "Upgrade Your System" in "Install from local file system" + Go to /acs-admin/install/ and click "Upgrade Your System" in "Install from local filesystem" Select all of the packages you want to upgrade and proceed @@ -339,11 +339,11 @@ - Upgrades work by first changing the file system (via any + Upgrades work by first changing the filesystem (via any of the previous methods), and then using the APM to scan the - file system, find upgrade scripts, and execute them. Starting + filesystem, find upgrade scripts, and execute them. Starting with OpenACS 5.0, the last method was added, which - automatically changes the file system for you. If you are + automatically changes the filesystem for you. If you are using the last method, you can skip this page. This page describes whether or not you need to be upgrading using this page or not: Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml,v diff -u -N -r1.14 -r1.14.2.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml 17 May 2018 12:12:32 -0000 1.14 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml 2 Jul 2020 08:39:25 -0000 1.14.2.1 @@ -977,7 +977,7 @@ 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. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml,v diff -u -N -r1.11 -r1.11.2.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 4 Jul 2018 10:20:42 -0000 1.11 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 2 Jul 2020 08:39:25 -0000 1.11.2.1 @@ -119,7 +119,7 @@ A registry of installed packages, database-backed and -integrated with file system-based version control +integrated with filesystem-based version control @@ -498,7 +498,7 @@ 4.600.1 Each package will have a PGP signature and there -will be MD5 time stamps for each file within the package. +will be MD5 timestamps for each file within the package. @@ -558,19 +558,19 @@ 20.1 The developer must be able to add files to the package. This is done by copying the files into the package directory in the -host OS's file system. Files can be added at any point after package +host OS's filesystem. Files can be added at any point after package creation. 20.3 Once a package has been versioned and distributed, no new files should be added to the package without incrementing the version number. 20.5 The APM's UI should facilitate the process of -adding new files, by scanning the file system for new files automatically, +adding new files, by scanning the filesystem for new files automatically, and allowing the developer to confirm adding them. 20.10 The developer cannot add files to a given package -via the UI that do not exist in the file system already. +via the UI that do not exist in the filesystem already. 20.15 Package file structure must follow a specified convention. Please see the design @@ -586,10 +586,10 @@ files. 30.1.1If a file is removed from the package list, but not -from the file system, an error should be generated at package load time. +from the filesystem, an error should be generated at package load time. -30.5 Remove the file from file system. +30.5 Remove the file from filesystem. 30.5.1 The APM UI should take note of the fact that the file is gone and offer the developer an option to confirm the file's @@ -603,7 +603,7 @@ 40.0 Modify files in a package. 40.1 The developer should be able to modify files in the -file system. The APM UI should not interfere with this. +filesystem. The APM UI should not interfere with this. 40.5 However, if the developer modifies files containing procedural definitions, APM UI should allow a means to watch @@ -648,8 +648,7 @@ specification that encodes all package information. -70.0 Write an XML package specification to the file -system +70.0 Write an XML package specification to the filesystem 70.1 The developer should be able to write an up-to-date XML specification to disk. @@ -837,7 +836,7 @@ the package. 110.1.5 Moving all of the files into a separate location -in the file system from the installed packages. +in the filesystem from the installed packages. 4.110.1.10 If the package is a compound package, then the administrator must confirm removing all sub-packages. Optionally, some @@ -871,11 +870,9 @@ 150.0 Scan for new or modified packages -150.1 The administrator should be able to scan the file -system for any changes made in any of the installed package files. +150.1 The administrator should be able to scan the filesystem for any changes made in any of the installed package files. -150.5 The administrator should be able to scan the file -system for any newly installed packages. +150.5 The administrator should be able to scan the filesystem for any newly installed packages. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml,v diff -u -N -r1.13.2.4 -r1.13.2.5 --- openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml 17 Dec 2019 16:53:18 -0000 1.13.2.4 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml 2 Jul 2020 08:39:25 -0000 1.13.2.5 @@ -2036,8 +2036,7 @@ containing user information. Example mechanisms: - A file is delivered to an agreed-on location in the file -system at an agreed-on point in time. + A file is delivered to an agreed-on location in the filesystem at an agreed-on point in time. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml,v diff -u -N -r1.8.2.2 -r1.8.2.3 --- openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml 9 Aug 2019 20:04:23 -0000 1.8.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml 2 Jul 2020 08:39:25 -0000 1.8.2.3 @@ -256,8 +256,7 @@ Authentication Driver, e.g. "RADIUS". In practice, this would be a reference to a service contract implementation. - Authentication Driver configuration settings, e.g. host - name, port, etc., as required by the particular driver. Note that + Authentication Driver configuration settings, e.g. hostname, port, etc., as required by the particular driver. Note that this is per authority, not per driver, i.e., you can have multiple authorities with the same driver but different configuration options. @@ -275,8 +274,7 @@ reason we have separate drivers for authentication and account creation is that organizations are likely to have a home-grown account registration process. - Account Creation Driver configuration settings, e.g. host - name, port, etc., as required by the particular driver. Note that + Account Creation Driver configuration settings, e.g. hostname, port, etc., as required by the particular driver. Note that this is per authority, not per driver, i.e., you can have multiple authorities with the same driver but different configuration options. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/groups-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/groups-requirements.xml,v diff -u -N -r1.8 -r1.8.2.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/groups-requirements.xml 25 Apr 2018 08:38:28 -0000 1.8 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/groups-requirements.xml 2 Jul 2020 08:39:25 -0000 1.8.2.1 @@ -225,7 +225,7 @@ The data model should enforce these constraints: - 40.10 A user must have a non-empty email address. + 40.10 A user must have a nonempty email address. 40.20 Two different users may not have the same email address on a single OpenACS installation; i.e., an email address identifies a Index: openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml,v diff -u -N -r1.12.2.1 -r1.12.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 10 Mar 2019 21:44:57 -0000 1.12.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 2 Jul 2020 08:39:25 -0000 1.12.2.2 @@ -655,27 +655,25 @@
90.10 Provide API support for specifying -a time zone +a timezone 90.20 Provide an API for computing time and date operations which are aware of timezones. So for example a calendar module can properly synchronize items inserted into a -calendar from users in different time zones using their own local +calendar from users in different timezones using their own local times. 90.30 Store all dates and times in -universal time zone, UTC. +universal timezone, UTC. -90.40 For a registered users, a time -zone preference should be stored. +90.40 For a registered users, a timezone preference should be stored. -90.50 For a non-registered user a time -zone preference should be attached via a session or else UTC should +90.50 For a non-registered user a timezone preference should be attached via a session or else UTC should be used to display every date and time. 90.60 The default if we can't -determine a time zone is to display all dates and times in some -universal time zone such as GMT. +determine a timezone is to display all dates and times in some +universal timezone such as GMT.
Database Index: openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml,v diff -u -N -r1.11.2.1 -r1.11.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml 14 Aug 2019 07:36:04 -0000 1.11.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml 2 Jul 2020 08:39:25 -0000 1.11.2.2 @@ -474,7 +474,7 @@ alternative. Here, some notion of subtyping is embedded into an existing SQL or SQL-like database engine. Examples of systems like this include the new Informix, PostgreSQL 7, and Oracle has something like this too. The main -problem with these systems: each one implements their own non-portable +problem with these systems: each one implements their own nonportable extensions to SQL to implement subtyping. Thus, making OpenACS data models portable would become even more difficult. In addition, each of these object systems have strange limitations that make using inheritance difficult in @@ -499,7 +499,7 @@ that the data model is not designed to scale too large type hierarchies. In the more limited domain of the metadata model, this is acceptable since the type hierarchy is fairly small. But the object system data model is not -designed to support, for example, a huge type tree like the Java runtime +designed to support, for example, a huge type tree like the Java run time libraries might define. This last point cannot be over-stressed: the object model is not Index: openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml,v diff -u -N -r1.8 -r1.8.2.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml 25 Apr 2018 08:38:28 -0000 1.8 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml 2 Jul 2020 08:39:25 -0000 1.8.2.1 @@ -213,7 +213,7 @@ model, or how to store information that may change extensively between releases or in different client installations. Furthermore, we want to avoid changes to an application's database queries in the face of any custom -extensions, since such changes are difficult or dangerous to make at runtime, +extensions, since such changes are difficult or dangerous to make at run time, and can make updating the system difficult. Some example applications in OpenACS 3.x with modifiable data models include: Index: openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml,v diff -u -N -r1.11.2.1 -r1.11.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml 5 Oct 2019 13:43:47 -0000 1.11.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml 2 Jul 2020 08:39:25 -0000 1.11.2.2 @@ -111,7 +111,7 @@ abstract file or abstract path -- A URL -that has been translated into a file system path (probably by prepending the +that has been translated into a filesystem path (probably by prepending the appropriate pageroot), but still doesn't have any extension and so does not directly correspond to a file in the filesystem. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml,v diff -u -N -r1.7.16.1 -r1.7.16.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml 5 Oct 2019 13:43:47 -0000 1.7.16.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml 2 Jul 2020 08:39:25 -0000 1.7.16.2 @@ -410,8 +410,8 @@ The users table is updated by sec_update_user_session_info which is called -when an existing session is assigned a non-zero user_id, or when a session is -created with a non-zero user_id. +when an existing session is assigned a nonzero user_id, or when a session is +created with a nonzero user_id. @@ -455,7 +455,7 @@ these values are used to dynamically generate a procedure that returns a constant. This approach avoids (relatively) expensive calls to ad_parameter in sec_handler. The impact of this -approach is that these parameters cannot be dynamically changed at runtime +approach is that these parameters cannot be dynamically changed at run time and require a server restart.