Developing applications over IPX/SPX using TLI

SAP services

SAP provides a way for service nodes to register their services and addresses in a Server Information table. This table is maintained by SAPD. Clients can query this table for available services and their addresses.

SAP is always up to date because it supports the dynamic registering of services. As services are booted up, they register themselves using SAP. When they are brought down, they use SAP to indicate that their services are no longer available. SAP removes those services from the Server Information table.

NOTE: Updates to the Server Information table are not immediate.

NetWare clients cannot initiate a session with a service without first knowing the address of that service. SAP provides methods for obtaining these addresses. Clients can either query a SAP agent or the bindery of a file server.

SAP agents

All NetWare file servers and routers have a SAP agent. The SAP agent for SCO IPX/SPX is SAPD. SAP agents:

All services are grouped together according to the types of services. Depending upon the type of query, a SAP agent returns one of the following: The SAP agent provides faster access to information about types of servers than does the bindery.

NetWare bindery queries

SCO IPX/SPX can be used to query a NetWare server's bindery, but a general programmatic interface to Novell's bindery or NetWare Directory Services (NDS) is not currently part of IPX/SPX. Information regarding the structure of the bindery or NDS queries and responses can be obtained from Novell.

Next topic: The Service Advertising Protocol daemon SAPD
Previous topic: Using the SAP protocol

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003