• Artigo

CommunicationState Enumeration

Microsoft Silverlight will reach end of support after October 2021. Learn more.

Defines the states in which an ICommunicationObject can exist.

Namespace:  System.ServiceModel
Assembly:  System.ServiceModel (in System.ServiceModel.dll)

Syntax

'Declaration
Public Enumeration CommunicationState

public enum CommunicationState

Members

Member name Description
Supported by Silverlight for Windows Phone Created Indicates that the communication object has been instantiated and is configurable, but not yet open or ready for use.
Supported by Silverlight for Windows Phone Opening Indicates that the communication object is being transitioned from the Created state to the Opened state.
Supported by Silverlight for Windows Phone Opened Indicates that the communication object is now open and ready to be used.
Supported by Silverlight for Windows Phone Closing Indicates that the communication object is transitioning to the Closed state.
Supported by Silverlight for Windows Phone Closed Indicates that the communication object has been closed and is no longer usable.
Supported by Silverlight for Windows Phone Faulted Indicates that the communication object has encountered an error or fault from which it cannot recover and from which it is no longer usable.

Remarks

This enumeration defines the states that are valid for all communication objects in the system, including channels, listeners, factories, dispatchers, and service hosts.

The methods that manage transitions between these states and the events that can be associated with them are defined in the ICommunicationObject interface. The state of an object can be obtained using the State property.

There are four main states and two transient states that a communication object can occupy. The main states are:

  • Created

  • Opened

  • Closed

  • Faulted

The two transitory states that a communication object can occupy when transitioning between these main states are:

  • Opening

  • Closing

The communication object can be configured in the Created state. For example, its properties can be changed and its events can be registered. No input or output can occur in this state. So messages, for example, cannot be sent or received from a channel in this state.

The Opening is a temporary state that the communication object enters when the Open method is invoked. Unless otherwise noted on derived classes, objects in the opening state cannot be configured. This transition state can only be entered from the Created state.

Objects transition to the Opened state when the open process completes. This transition to the Opened state is valid only from the Opening state. Unless otherwise noted on derived classes, the configuration of the object is now disabled. At this point, the object is fully usable for message transfers.

The Closing is a temporary state that the object enters when the Close method is invoked for a graceful shutdown or the object is aborted. At this point, the object becomes (if not already) unusable. This transition is valid from any state except the Closed state.

The Closed state is equivalent to being disposed and the configuration of the object can still be inspected.

The Faulted state is used to indicate that the object has transitioned to a state where it can no longer be used. There are two primary scenarios where this can happen:

  • If the Open method fails for any reason, the object transitions to the faulted state.

  • If a session-based channel detects an error that it cannot recover from, it transitions to the faulted state. This can happen, for instance, if there is a protocol error (that is, it receives a protocol message at an invalid time) or if the remote endpoint aborts the session.

An object in the Faulted state is not closed and might be holding resources. The Abort method should be used to close an object that has faulted. If Close is called on an object in the Faulted state, a CommunicationObjectFaultedException is thrown because the object cannot be gracefully closed.

Version Information

Silverlight

Supported in: 5, 4, 3

Silverlight for Windows Phone

Supported in: Windows Phone OS 7.1, Windows Phone OS 7.0

XNA Framework

Supported in: Windows Phone OS 7.0

Platforms

For a list of the operating systems and browsers that are supported by Silverlight, see Supported Operating Systems and Browsers.

See Also

Reference

System.ServiceModel Namespace