![]() |
![]() |
|
|
Specifying How Clients Receive Unsolicited Notification
You can select the default method by which clients receive unsolicited messages by setting the NOTIFY parameter. The client, however, can override this choice when calling tpinit().
Following are four possible methods:
Note: This method is not allowed for multithreaded or multicontexted applications.
The USIGNAL parameter specifies the signal to be used if SIGNAL-based notification is used. Two types of signals can be generated: SIGUSR1 and SIGUSR2. The default is SIGUSR2. This method has the advantage of immediate notification, but is limited when you are running a native client. In that case, you must have the same user ID as the sending process. Workstation clients do not have this limitation.
Note: This method is not available on all platforms.
Characteristics of the NOTIFY and USIGNAL Parameters
![]() |
![]() |
![]() |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|