wcf - WS Addressing and Multiple "ReplyTo" -

Please explain to me whether or not it supports multiple responsibilities while addressing WSF in WSF.

This will answer in depth to your question

...

Multiple Endpoint and Unique Addresses

There are a few reasons why you may want to expose many endpoint points to a particular service. One reason is to expose the same contract by using a few different bindings. For example, you may have some users who only have WS-I Basic Profile 1.1-compliant service (one binding) and others that have full suite of standards (other Binding) can work with. Or do you have some internal enterprise consumers who ask for binary TCP transmission for performance reasons (another binding). The ability to highlight the same contract using different bindings allows you to adjust all these consumers at the same time. While highlighting several finishing points with different bindings, each endpoint address should be unique. This is because each endpoint requires a separate transport listener and channel stack. Consider service configuration in Figure 4. In this example, the same contract (iisipalmath) of all the finishing points is exposed, but each uses a different bond, so each address must be unique. If you modify the endpoint to use the same address as another endpoint, Windows Communications Foundation throws an exception when opening the service host.

...