Mixed Mode Serialization of Context Handles
Starting with Windows XP, a single interface can accommodate both serialized and nonserialized context handles, enabling one method on an interface to access a context handle exclusively (serialized), while other methods access that context handle in shared mode (nonserialized). For more information about context handles, see the following attributes:
Serialized and shared mode access capabilities are comparable to read/write locking mechanisms; methods using a serialized context handle are exclusive users (writers), whereas methods using a nonserialized context handle are shared users (readers). Methods that destroy or modify the state of a context handle must be serialized. Methods that do not modify the state of a context handle, such as those methods that simply read from a context handle, can be nonserialized. Using a context handle in mixed mode can substantially improve the scalability of a server, especially when multiple threads make simultaneous calls to the same context handle.
RPC does not enforce "write lock" on methods using a context handle in shared mode, which means applications must ensure that shared mode context handles are not modified. Modification of a context handle used in shared mode can result in subtle corruptions of context handle contents, which are impossible to debug.
Changing the serialization logic of a context handle affects only the server. Also, changing the serialization logic of a context handle does not affect the wire format, and therefore, changes to serialization logic on a server do not affect existing clients' capability to interact with the server.
Using only nonserialized context handles is not recommended. Servers that use nonserialized handles are should switch to serialized access for the method that closes the context handle.
Context handles that are [out]-only are typically used by creation methods, and do not require any serialization. Therefore, any serialization attribute applied to [out]-only context handles, such as context_handle_serialize or context_handle_noserialize, is ignored by RPC.
Note Creation methods are implicitly serialized.
The following two examples show how to enable mixed mode serialization of context handles.
The first example shows how to do so in the IDL file:
typedef [context_handle] void *TestContextHandleExclusive; typedef [context_handle] TestContextHandleExclusive TestContextHandleShared; void UseShared(... [in] TestContextHandleShared *Ctx, ...); void UseExclusive(... [in, out] TestContextHandleExclusive *Ctx, ...);
The second example shows how to enable mixed mode serialization of context handles in the ACF file:
typedef [context_handle_serialize] TestContextHandleExclusive; typedef [context_handle_noserialize] TestContextHandleShared;
Build date: 11/27/2013