OSF DCE Application Development Guide--Core Components

Attribute Configuration Language
ACF
typedef [cs_char(ltype)] my_byte;
[cs_tag_rtn(set_tags)] a_op( [cs_stag] stag,
[cs_drtag] drtag,
[cs_rtag] p_rtag );
b_op( [cs_stag] stag,
[cs_drtag] drtag,
[cs_rtag] p_rtag );
Generated Header File
typedef byte my_byte;
void a_op(
/* [in] */ idl_long_int s,
/* [in, out] */ idl_long_int *p_l,
/* [in, out, size_is(s), length_is(*p_l)] */ ltype a[]
);
void b_op(
/* [in] */ idl_ulong_int stag,
/* [in] */ idl_ulong_ing drtag,
/* [out] */ idl_ulong_int *p_rtag,
/* [in] */ idl_long_int s,
/* [in, out] */ idl_long_int *p_l,
/* [in, out, size_is(s), length_is(*p_l)] */ ltype a[]
);
18.3.17 The binding_callout Attribute
The binding_callout attribute permits you to specify the name of a routine that the
client stub is to call automatically to modify a server binding handle before it initiates a
remote procedure call. This attribute is intended for use by client applications that
employ the automatic binding method through the auto_handle ACF interface attribute.
In automatic binding, it is the client stub, rather than the client application code, that
obtains the binding handle to the server. The binding_callout attribute allows a client
application using automatic binding to modify the binding handle obtained by the client
stub. Without this attribute, it is impossible for the client application to modify the
binding handle before the client stub attempts to initiate a remote procedure call to the
selected server.
Clients typically use this attribute to augment automatic binding handles with security
context, for example, so that authenticated RPC is used between client and server.
124245 Tandem Computers Incorporated 18− 27