| Prev | Chapter 11. Development Reference | Next |
|---|
By Pete Su
-======= -By Pete Su
->>>>>>> 1.47 +-This document is a brief introduction to the OpenACS 5.6.0 Request Processor; -more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high level concepts behind the -=======
This document is a brief introduction to the OpenACS 5.6.0 Request Processor; more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high level concepts behind the ->>>>>>> 1.47 system, and implications and usage for the application developer. -<<<<<<< request-processor.html -
-The 5.6.0 Request Processor is a global filter and set of Tcl procs that -=======
The 5.6.0 Request Processor is a global filter and set of Tcl procs that
->>>>>>> 1.47
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.
@@ -33,25 +17,15 @@
The first thing the RP does is to map the given URL to the appropriate physical directory in the filesystem, from which to serve content. We -<<<<<<< request-processor.html -do this by searching the site map data model (touched on in the Packages, and further -discussed in Writing OpenACS Application Pages). This data model maps URLs to objects representing -======= do this by searching the site map data model (touched on in the Packages, and further discussed in Writing OpenACS Application Pages). This data model maps URLs to objects representing ->>>>>>> 1.47 content, and these objects are typically package instances.
After looking up the appropriate object, the RP stores the URL, the ID
of the object it found, and the package and package instance the
object belongs to into the environment of the connection. This
-<<<<<<< request-processor.html
-environment can be queried using the ad_conn procedure,
-which is described in detail in OpenACS 4 Request Processor Design. The page
-=======
environment can be queried using the ad_conn procedure,
which is described in detail in OpenACS 4 Request Processor Design. The page
->>>>>>> 1.47
development tutorial shows you how to use this interface to make
your pages aware of which instance was requested.
@@ -62,15 +36,9 @@ extracts or sets up new session tokens for the user.
Next, the Request Processor checks if the user has appropriate access -<<<<<<< request-processor.html privileges to the requested part of the site. In OpenACS 5.6.0, access control -is dictated by the permissions system. In -this case, the RP checks if the user has "read" priviledges on the -======= -privileges to the requested part of the site. In OpenACS 5.6.0, access control is dictated by the permissions system. In this case, the RP checks if the user has "read" priviledges on the ->>>>>>> 1.47 object in the site map specified by the URL. This object is typically a package instance, but it could easily be something more granular, such as whehter the user can view a particular piece of content within @@ -159,8 +127,4 @@
In a .vuh file, path_info is the trailing part of the URL not matched by the .vuh file. -<<<<<<< request-processor.html