HP DCE/9000 Version 1.7 Application Development Tools for HP-UX 11.0 Release Note

HP DCE 1.7 Application Development Tools Release Note 39
Developing DCE Applications with HP DCE/ 9000
Notes on Programming with HP DCE
manager access function will have to make an access decision based
on this fact. Note that in such a case, no meaningful authentication or
authorization information is returned from
rpc_binding_inq_auth_client().
RPC Data Transfer Limitation
The bulk data transfer (for example, IN/OUT-pipes) over the
connection-oriented (TCP/IP) RPC protocol is limited by the performance
difference between the client and server machines. If the receiver process
is significantly slower than the sender process (and cannot process data
fast enough), the receiver process's virtual memory usage may grow
rapidly until the remote procedure call fails with an rpc_s_no_memory
status.
Restricting RPC Addresses
The runtime looks for a RPC_SUPPORTED_NETADDRS environment
variable, which allows a user or administrator to restrict the network
addresses that a DCE server will advertise in the name
space/endpoint-map.
If this environment variable is set, only addresses in the list will be
advertised in the name space or endpoint map. Addresses not found on
the list will be excluded from the server's list of available addresses.
The format of the RPC_SUPPORTED_NETADDRS string is as follows:
RPC_SUPPORTED_NETADDRS=protseq:netaddr[,protseq:netaddr]
For example, assuming that host myhost is located at IP address
10.3.2.1, the Korn shell statements:
export RPC_SUPPORTED_NETADDRS=ip:myhost
or
export RPC_SUPPORTED_NETADDRS=ip:10.3.2.1
will force any servers started in the current shell to support only the
addresses associated with the name myhost and the network address
10.3.2.1.