Should WCF mex endpoint types match the service endpoint type?

Here is web.config for my WCF endpoint:

<services>
      <service behaviorConfiguration="SearchQueryServiceBehavior" 
       name="Search.Querier.WCF.Querier">
      <endpoint address="mex" binding="mexHttpBinding" name="mexHttpEndpoint"
        contract="IMetadataExchange" />
      <endpoint binding="netTcpBinding" bindingConfiguration="" 
       name="netTcpEndpoint"
        contract="Search.Querier.WCF.IQuerier" />
      </service>
</services>

Does it matter if I plan to use netTCpEndpoint, do I need a mexTCPEndpoint, or can it be Http?

+3
source share
2 answers

You can have as many endpoints as you want, so I don’t see how this can make a difference. Damn, why not be nice to users and offer both HTTP and TCP mex bindings.

+2
source

MEX . wsHttp, , netTcp . , , MEX , , , MEX, , , .;)

+3

Source: https://habr.com/ru/post/1718569/


All Articles