Index: openacs-4/packages/acs-developer-support/www/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-developer-support/www/doc/index.html,v diff -u -r1.1.1.1 -r1.1.1.1.28.1 --- openacs-4/packages/acs-developer-support/www/doc/index.html 20 Apr 2001 20:51:09 -0000 1.1.1.1 +++ openacs-4/packages/acs-developer-support/www/doc/index.html 21 Aug 2015 10:28:44 -0000 1.1.1.1.28.1 @@ -4,7 +4,7 @@ -

Developer Support

+

Developer Support

part of the ArsDigita Community System, by Jon Salz @@ -20,14 +20,14 @@ -

The Big Picture

+

The Big Picture

Software development is a big feedback loop: a developer writes something, tests it, and then repeats until the results are satisfactory. It's important to streamline this cycle by having a development environment which makes it easy to analyze what the software is doing under the hood. -

Peeking Under the Hood

+

Peeking Under the Hood

Our development environment previously consisted largely of Emacs, and tail -f /web/servername/log/servername-error.log. Now this has been augmented: @@ -52,7 +52,7 @@ administrator! Revealing this information to anyone else would pose a huge security risk. -

Comments

+

Comments

Tired of using ns_log to instrument your code, then grokking the error log to see what's wrong with your page? Use the ds_comment routine instead: @@ -84,13 +84,16 @@ Note that you may not want to enable this stuff for production systems - they probably incur a slight performance hit (although this hasn't been benchmarked). -

How It Works

+

How It Works

The security subsystem registers preauth and trace filters which store relevant connection information in shared variables (nsvs). The security subsystem also renames the AOLserver ns_db procedure and registers a wrapper which aggregates information about database queries. +

Release Notes

+ +

Please file bugs in the Bug Tracker.


jsalz@mit.edu