DCE Application Programming Guide

Application Design Considerations
HP NonStop DCE Application Programming Guide—429551-003
2-7
Access to Non-DCE Servers
Because this intermediate process is a DCE client that uses process-blocking
functions, it should use only ncacn_ip_tcp, a connection-oriented RPC protocol
sequence.
Access to Non-DCE Servers
DCE clients and servers can access non-DCE Guardian and Pathway servers using
the standard Guardian procedures (such as WRITEREAD) or the
SERVERCLASS_SEND_ jacket (the DCE_SERVERCLASS_SEND_() function),
SERVERCLASS_DIALOG_BEGIN_ jacket (the
DCE_SERVERCLASS_DIALOG_BEGIN_() function),
SERVERCLASS_DIALOG_SEND_ jacket (the
DCE_SERVERCLASS_DIALOG_SEND_() function), SERVERCLASS_DIALOG_END_
jacket (the DCE_SERVERCLASS_DIALOG_END_() function),
Figure 2-1. Accessing a DCE Server Using an Intermediate Server Class
VST002.vdd
SERVERCLASSSEND( )
.
.
.
.
Guardian Process
READUPDATE()
$RECEIVE
Map message fields
to input parameters
Issue RPC
Map output
parameters to
message fields
REPLY()
Single-threaded OSS processes
written in C
Process
incoming
RPC
Application call
threads of
DCE Server
Process