Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml,v diff -u -r1.5 -r1.6 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml 30 Nov 2002 17:16:52 -0000 1.5 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml 24 Jun 2003 03:37:04 -0000 1.6 @@ -15,43 +15,9 @@ -The Old Way +Request Processor -In older versions of the OpenACS, the mapping between URLs and pages was -simple. AOLserver, the usual webserver for the OpenACS, would find the -appropriate file by appending the server's page-root to the path in -the URL and returning that file to the user. For example, a user's -request for a URL like "http://foo-service.com/bar.html" would cause -the server to look in the filesystem for -/web/foo-service/www/bar.html, and return that file. -This was simple enough, but OpenACS did not provide a clean centralized -mechanism for the following requirements of larger web services: - - - - Support for more flexible mappings from URLs to content - - Robust user authentication - - Page level access control - - - - -To achieve this functionality above in OpenACS 3.x, developers used an ad -hoc combination of AOLserver filters, the ns_perm call, -special purpose code in pages, and other procedures. In OpenACS &version;, the -Request Processor, along with the OpenACS Package Manager, centralizes and -unifies this functionality, making it more transparent and readily -available to developers. - - - - -The New Way - - The &version; Request Processor is a global filter and set of Tcl procs that respond to every incoming URL reaching the server. The following diagram summarizes the stages of the request processor assuming a URL