XmlBinaryWriterSession Class
[ This article is for Windows Phone 8 developers. If you’re developing for Windows 10, see the latest documentation. ]
Enables using a dynamic dictionary to compress common strings that appear in a message and maintain state.
Assembly: System.Runtime.Serialization (in System.Runtime.Serialization.dll)
The XmlBinaryWriterSession type exposes the following members.
| Name | Description | |
|---|---|---|
![]() | Equals(Object) | Determines whether the specified Object is equal to the current Object. (Inherited from Object.) |
![]() | Finalize | Allows an object to try to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.) |
![]() | GetHashCode | Serves as a hash function for a particular type. (Inherited from Object.) |
![]() | GetType | Gets the Type of the current instance. (Inherited from Object.) |
![]() | MemberwiseClone | Creates a shallow copy of the current Object. (Inherited from Object.) |
![]() | Reset | Clears out the internal collections. |
![]() | ToString | Returns a string that represents the current object. (Inherited from Object.) |
![]() | TryAdd | Tries to add an XmlDictionaryString to the internal collection. |
Session objects (this class together with XmlBinaryReaderSession) enable dynamic string atomization that can span an entire conversation. These session objects manage dynamic dictionaries. For more information about dynamic dictionaries, see XmlDictionary.
Due to asynchronous processing, it is possible for messages that arrive synchronously to be processed in a different order than the order in which they were sent. String atomization that spans messages must ensure that the messages are processed in the original order or the atomized strings must be conveyed using a different mechanism.
To use them, you create a session object and pass it to the constructor or initializer for a binary XML reader or writer.

