When you use procedure serialization, a procedure is labeled with the [encode] or [decode] attribute. Instead of generating the usual remote stub, the compiler generates a serialization stub for the routine.
Just as a remote procedure must use a binding handle to make a remote call, a serialization procedure must use a serialization handle to use serialization services. If a serialization handle is not specified, a default implicit handle is used to direct the call. On the other hand, if the serialization handle is specified, either as an explicit handle_t argument of the routine or by using the [explicit_handle] attribute, you must pass a valid handle as an argument of the call. For additional information on how to create a valid serialization handle, see Serialization Handles, Examples of Fixed Buffer Encoding, and Examples of Incremental Encoding.
Note: Microsoft RPC allows remote and serialization procedures to be mixed in one interface. However, use caution when doing so.
For remote procedures with implicit binding handles, the MIDL compiler generates a global handle variable of type handle_t. Procedures and types with implicit serialization handles use this same global handle variable.
For implicit handles, the global implicit handle must be set to a valid binding handle before a remote call. The implicit handle must be set to a valid serialization handle before a serialization call. Therefore, a procedure cannot be both remote and serialized. It must be one or the other.
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
