Previous | Contents | Index |
In order to customize the management interface, it is first necessary to understand how the CGIs process HTTP requests and formulate HTTP responses. This is described in Section 4.3.1 and Section 4.3.2. Section 5.2.1 describes the individual commands which can be embedded in those requests.
5.2.1 User Interface Commands
When a command is sent to the user interface, the command is applied to
the popstore/MessageStore account whose name is given with the HTTP
authentication. That is, the HTTP command carries with it a
popstore/MessageStore username and password. If the username and
password are valid, then the command is applied to the
popstore/MessageStore account denoted by the username.
As described in Section 4.3.1, commands take the general form
command=command-name¶meter-name-1=parameter-value-1& ...¶meter-name-N=parameter-value-N |
command-name
gives the name of the command to execute. It is then followed by two or
more parameters which provide supplemental information relevant to the
operation to be performed. When parameter names are duplicated in the
command, only the right most instance of the parameter=value pair is
honored.
For those parameters whose values are file specifications, the file specifications must be relative file paths specifying files in the /pmdf/www/msps_user/
or /pmdf/www/chng_pwd/
directory trees on UNIX and NT systems, or the directories PMDF_ROOT:[WWW.MSPS_USER]
and PMDF_ROOT:[WWW.CHNG_PWD]
on OpenVMS systems.
The valid command names are listed in the table below and described in the following sections.
Command name | Section | Description |
---|---|---|
delete
|
5.2.1.1 | Delete a message stored for the user (popstore only) |
set_pwd
|
5.2.1.3 | Change the password for the user |
show
|
5.2.1.2 | Show a message stored for the user (popstore only) |
show_user
|
5.2.1.4 | Show settings for the user account |
Previous | Next | Contents | Index |