|Oracle Call Interface Programmer's Guide
Part Number A89857-01
More OCI Relational Functions, 41 of 97
Posts to a subscription which allows all clients who are registered for the subscription to get notifications.
ub4 OCISubscriptionPost ( OCISvcCtx *svchp, OCISubscription **subscrhpp, ub2 count, OCIError *errhp ub4 mode );
An OCI service context (after release 7). This service context should have a valid authenticated user handle.
An array of subscription handles. Each element of this array should be a subscription handle with the OCI_ATTR_SUBSCR_NAME and OCI_ATTR_SUBSCR_NAMESPACE attributes set.
For information, see Subscription Handle Attributes
The OCI_ATTR_SUBSCR_PAYLOAD attribute has to be set for each subscription handle prior to this call. If it is not set, the payload is assumed to be
NULL and no payload is delivered when the notification is received by the clients that have registered interest. Note that the caller will have to preserve the payload until the post is done as the
OCIAttrSet() call keeps track of the reference to the payload but does not copy the contents.
The number of elements in the subscription handle array.
An error handle you can pass to
OCIErrorGet() for diagnostic information in the event of an error.
Call-specific mode. Valid value:
Posting to a subscription involves identifying the subscription name and the payload if desired. If no payload is associated, the payload length can be set to 0.
This call provides a best-effort guarantee. A notification does to registered clients at most once.
This call is primarily used for light-weight notification and is useful in the case of several system events. If the application needs more rigid guarantees, it can use the Advanced Queuing functionality by enqueuing to queue.