TRANSFER Programming Manual

Registering a Correspondent
Designing and Writing a Client
9–2 069138, Update 1 to 040970 Tandem Computers Incorporated
Registering a
Correspondent
An application must register any new correspondent at the same node as the TISERV
process through which the application requests this registration. Registration is
requested by a process running on behalf of the system administrator for the node.
When an application requests this registration, the TRANSFER delivery system places
the name of the correspondent in the name directory. At this time, the TRANSFER
delivery system also creates a depot for the correspondent which consists of
correspondent profiles and the three special folders, INBOX, OUTLOG, and
WASTEBASKET.
Initiating a Session To represent a correspondent, a client must first initiate a session for that
correspondent; this establishes communication between the correspondent and the
TRANSFER delivery system. The client directs its request for a session to a TISERV
server at the node where the correspondent is registered. The TRANSFER delivery
system validates the correspondent name and password supplied by the client. The
TRANSFER delivery system then starts the session at that node. The session cannot be
passed to servers at any other node.
To establish a session, issue a START-SESSION UOW to TISERV and supply the name
and password of the correspondent that the requester represents. TISERV must be
running at the node where the correspondent resides.
A session provides communication between a correspondent and The TRANSFER
delivery system. As illustrated in Figure 9-1, the session includes transactions to send
a package, but does not include the routing and delivery of packages to depots.
Because of the TRANSFER nowait feature, neither the sender nor any recipient of a
package needs to have a session in progress while the package is in transit or when it
arrives at a depot. A correspondent terminates the session when services are no longer
required for the depot.
When a requester initiates a session, TISERV returns a session ID to the requester.
This ID, which is unique throughout the network, must occur in every later request
that the requester makes for the correspondent. Eventually the process terminates the
session, perhaps because the correspondent logged off, and relinquishes the session
ID.