System.ServiceModel 4.0.0.0 System.Enum This enumeration is used to specify the capability of a server, which, in turn, imposes a requirement on its clients. indigo1 has a variety of addressing controls for specifying where messages should be sent. For example, there is the logical address for the message destination, the physical ("Via") address, used by the transport, at which a service listens, and the address of the endpoint that provides the address of the client endpoint. In the most basic case, when two parties exchange messages between themselves only, it is not necessary to specify these addresses separately. But because exchanges can involve other message destinations, you must be able to specify when addresses must be explicitly provided. Even between just two parties this ability is sometimes required, as with dual HTTP where the server must create its own HTTP request. The following kinds of relationships are defined by the enumeration to capture these messaging patterns: addresses are the most basic form of addressing. Anonymous addressing is used when there is a default path for a response. TCP is a bi-directional communication transport and the response to a TCP message can be sent back to the other side of the socket that sent the original message. Similarly, the request-reply model of HTTP sends responses through the HTTP reply channel. Neither of these responses requires specifying where the response messages are going. When a server requires anonymous responses from the client, it uses the value of the enumeration. The indigo2 system-provided , and bindings always use addresses. addresses are used when sending the response requires creating a new channel for communication. The indigo2 system-provided binding uses a address. With dual HTTP, the client creates an HTTP request to send a message and then the server must create its own HTTP request to send a response. Because the server is initiating the send, it must have a specific endpoint to establish the connection. You must provide the server the address of an endpoint for its response. Similarly, if a service must respond to a one-way message that it received, it also requires a address because there is no back channel available for communication. If the server sends a message back, a completely separate operation from that used to send the first message is required. is a third form of addressing which combines and addresses depending on the message that is being sent. A typical example of mixed-mode addressing is the use of a dedicated machine for processing fault or acknowledgment messages. If the standard exchange sequence for replies is HTTP or TCP, the responses use addressing but the faults use non-anonymous addressing. While indigo2 does not provide addressing functionality in one of its standard bindings, it is possible to write a channel that allows the service to send responses directly on the back-channel (when the response address is ) or on a separate channel (when the response address is ). In such a case, the binding element of the channel is used to set to .

Specifies whether a service supports sending responses to anonymous addresses only, to non-anonymous addresses only, or to both.

Field 4.0.0.0 System.ServiceModel.Channels.SupportedAddressingMode

The server only supports anonymous addresses and clients must provide an anonymous response address.

Field 4.0.0.0 System.ServiceModel.Channels.SupportedAddressingMode

The server supports both anonymous and non-anonymous addresses and clients may choose to use either or both.

Field 4.0.0.0 System.ServiceModel.Channels.SupportedAddressingMode

The server only supports non-anonymous addresses and clients must provide a non-anonymous response address.