HP-UX SNAplus2 CPI-C Programmer's Guide (June 2003)

Writing CPI-C Applications
CPI-C Call Summary
Chapter 272
appropriate conversation; theprogram then calls Wait_For_Conversation
to get the results of the nonblocking function. This call enables the
program to check for completion of nonblocking functions without having
to suspend (unlike Wait_For_Conversation, which suspends until a
function has completed). Check_For_Completion does not return the
results of the previous call; the program must use
Wait_For_Conversation to do this before it can issue further calls on this
conversation.
End of Section Wait_For_Conversation (cmwait)
This call waits for processing of a previous nonblocking function to
complete. If the program is involved in multiple concurrent
conversations, this call acts across all conversations, and returns when a
function completes on any of them.
For Windows The Wait_For_Conversation call is supported on Windows systems for
compatibility with other Windows CPI-C implementations; however, new
Windows applications should use Specify_Windows_Handle (described
below) instead of this call.
Specify_Windows_Handle (xchwnd)
This call specifies a Windows handle to which CPI-C posts the results of
nonblocking functions. The application receives a message from CPI-C,
sent to this Windows handle, when a nonblocking function completes; it
does not need to use Wait_For_Conversation to obtain the results of verb
completion.
Issuing Calls in Blocking Mode
The following calls enable a Windows program to manage how
subsequent CPI-C calls operate in blocking mode. (See also
“Set_Processing_Mode (cmspm)”; this specifies whether subsequent calls
operate in blocking mode or nonblocking mode.) For more information
about blocking calls, see “Blocking Calls”.
WinCPICIsBlocking() Checks whether there is a blocking CPI-C call
outstanding for this application.