in parameters
For all pointer types, the client application must allocate memory for the pointed-to nodes.
out parameters
For reference pointers, the client application must allocate memory for the pointed-to nodes, unless the pointer is part of a data structure created by server
manager code. For parameters containing full pointers, the stub allocates memory for the pointed-to nodes.
in,out parameters
For reference pointers, the client application must allocate memory for the pointed-to nodes. For full pointers, on making the call, the client application
must allocate memory for the pointed-to node. On return, the stub keeps track of whether each parameter is the original full pointer passed by the client, or a new pointer allocated by the server.
If a pointer is unchanged, the returned data overwrites the existing pointed-to node. If a pointer is new, the stub allocates memory for the pointed-to node. When a parameter contains pointers,
such as an element in a linked list, the stub keeps track of the chain of references, allocating nodes as necessary.
It is the client application's responsibility to free any memory allocated by the stub for new nodes. Clients can call the routine rpc_sm_client_free(\|) for this purpose.
If the server deletes or eliminates a reference to a pointed to node, an orphaned node may be created on the client side. It is the client application's responsibility to keep track of memory that it has allocated for pointed-to nodes and to deal with any nodes for which the server no longer has references.