| |
| | |
| What do I need to know about memory allocation when using the RPC libraries? |
|
| | |
| Product: Distinct RPC for C, C++, Delphi | Topic: General | Last updated: 3/31/2008 | | | | Q.: What do I need to know about memory allocation when using the RPC libraries? | A.: For CRPC Server applications, you need to use the hook we generated to free the memory that you allocated in your own routines.
For other memory blocks allocated in the Distinct CRPC DLLs, memory will be freed by the DLLs themselves.
For CRPC Client applications, you need to use clnt_freeres() or
xdr_free() to free the memory returned by clnt_call() or similar
calls for the rpc call result. The memory is allocated by
D32-RPC.DLL to hold the result, it cannot be freed by using
free() directly.
|
If you did not find what you are looking for:
|
![]() 
|
|
