Netscape ENTERPRISE SERVER 6.1, Manual

Page: 132 / 373

Required Behavior of SAFs for Each Directive
132 Netscape Enterprise Server NSAPI Programmer’s Guide • April 2002 (Draft)
The
rq
parameter is the primary mechanism for passing along information
throughout the request-response process. On input to a SAF,
rq
contains whatever
values were inserted or modified by previously executed SAFs. On output,
rq
contains any modifications or additional information inserted by the SAF. Some
SAFs depend on the existence of specific information provided at an earlier step in
the process. For example, a PathCheck SAF retrieves values in
rq->vars
which
were previously inserted by an AuthTrans SAF.
This section outlines the expected behavior of SAFs used at each stage in the
request handling process.
• Init SAFs
• AuthTrans SAFs
• NameTrans SAFs
• PathCheck SAFs
• ObjectType SAFs
• Service SAFs
• Error SAFs
• AddLog SAFs
Init SAFs
• Purpose: Initialize at startup.
• Called at server startup and restart.
•
rq
and
sn
are
NULL
.
• Initialize any shared resources such as files and global variables.
• Can register callback function with
daemon_atrestart()
to clean up.
• On error, insert
error
parameter into
pb
describing the error and return
REQ_ABORTED
.
• If successful, return
REQ_PROCEED
.