| Noemax.WCFX.Configuration Namespace > FiMessageEncodingElement Class : PermitStateful Property |
'Declaration <System.Configuration.ConfigurationPropertyAttribute(Name="permitStateful", Options=ConfigurationPropertyOptions.None, IsDefaultCollection=False, IsRequired=False, IsKey=False)> Public Property PermitStateful As System.Boolean
'Usage Dim instance As FiMessageEncodingElement Dim value As System.Boolean instance.PermitStateful = value value = instance.PermitStateful
[System.Configuration.ConfigurationProperty(Name="permitStateful",
Options=ConfigurationPropertyOptions.None,
IsDefaultCollection=false,
IsRequired=false,
IsKey=false)]
public System.bool PermitStateful {get; set;}
public read-write property PermitStateful: System.Boolean;
System.Configuration.ConfigurationPropertyAttribute(Name="permitStateful", Options=ConfigurationPropertyOptions.None, IsDefaultCollection=, IsRequired=, IsKey=) public function get,set PermitStateful : System.boolean
The same Noemax.WCFX.Channels.FastInfosetSessionMode must be used on both communicating sides.
Note that in order to use the stateful encoding mode it is required that (a) messages are encoded and decoded in the same order on both sides, (b) messages are encoded and decoded one by one and that no message is encoded or decoded in parallel with another, and (c) messages are always fully decoded and that no message is only partially decoded. Satisfying all three requirements is not always possible when using a full duplex bidirectional transport in a multi-threaded environment; using the stateful encoding mode in such conditions might lead to channel faults.
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2