You can apply these attributes to individual functionswithin the interface, and affect only that function:
| Attribute | Usage |
|---|---|
| message | The remote procedure call is to be treated as an asynchronous message from the client to the server. The client makes the call and returns immediately, while the actual call is handled by the message-queuing transport (ncadg_mq). |
| maybe | The client making this remote procedure call does not expect any response indicating delivery or completion of the call. This is in contrast to message operations where no response is expected but the delivery is guaranteed. |
| broadcast | The remote procedure call is to be sent to all of the servers on the network. The client accepts the first return and subsequent replies from other servers are discarded. |
| idempotent | The call does not change state and returns the same information each time it is called with the same input parameters. |
| callback | Designates a function that resides in the client application, that the server can call to obtain information from the client. |
| call_as | Maps a non-remotable function to a remote procedure call. |
| local | Designates a local procedure for which MIDL does not generate stub code. Not valid for object interface functions. |
On non-object interfaces, you can also apply the string, ptr, and context_handle attributes to a function to specify characteristics of the return value.