| Prev | Chapter 8. Development Reference | Next |
|---|
By Pete Su
+-This document is a brief introduction to the OpenACS 5.6.0 Request Processor; +This document is a brief introduction to the OpenACS 5.7.0 Request Processor; more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high level concepts behind the system, and implications and usage for the application developer.
-The 5.6.0 Request Processor is a global filter and set of Tcl procs that +The 5.7.0 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 request like http://someserver.com/notes/somepage.adp. @@ -36,7 +36,7 @@ extracts or sets up new session tokens for the user.
Next, the Request Processor checks if the user has appropriate access -privileges to the requested part of the site. In OpenACS 5.6.0, access control +privileges to the requested part of the site. In OpenACS 5.7.0, access control is dictated by the permissions system. In this case, the RP checks if the user has "read" priviledges on the object in the site map specified by the URL. This object is typically @@ -127,4 +127,4 @@
In a .vuh file, path_info is the trailing part of the URL not matched by the .vuh file. -