Databases
StackOverflow2013
Postsdbo
POMultiple Base Addresses and Multiple Endpoints in WCF
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMultiple Base Addresses and Multiple Endpoints in WCF
    primarykey
    data
    text
    <p>I'm using two bindings TCP and HTTP. I want to give <strong>mex</strong> data on both bindings. What I want is that the mexHttpBinding only exposes the HTTP services while the mexTcpBinding exposes TCP services only. Or is this possible that I access <strong>stats</strong> service only from HTTP binding and the <strong>eventLogging</strong> service from TCP?</p> <p>For Example:</p> <ul> <li><p>For TCP I should only have </p> <pre><code>net.tcp://localhost:9001/ABC/mex net.tcp://localhost:9001/ABC/eventLogging </code></pre></li> <li><p>For HTTP </p> <pre><code>http://localhost:9002/ABC/stats http://localhost:9002/ABC/mex </code></pre></li> </ul> <p>When I connect with any of the base address (using the WCF Test Client) I'm able to access all the services? Like when I connect with <strong><em>net.tcp://localhost:9001/ABC</em></strong> I'm able to use the services which are offered on the HTTP binding. Why is that so?</p> <pre><code>&lt;system.serviceModel&gt; &lt;services&gt; &lt;service behaviorConfiguration="ABCServiceBehavior" name="ABC.Data.DataServiceWCF"&gt; &lt;endpoint address="eventLogging" binding="netTcpBinding" contract="ABC.Campaign.IEventLoggingService" /&gt; &lt;endpoint address="mex" binding="mexTcpBinding" bindingConfiguration="" contract="IMetadataExchange" /&gt; &lt;endpoint address="stats" binding="basicHttpBinding" contract="ABC.Data.IStatsService" /&gt; &lt;endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /&gt; &lt;host&gt; &lt;baseAddresses&gt; &lt;add baseAddress="net.tcp://localhost:9001/ABC" /&gt; &lt;add baseAddress="http://localhost:9002/ABC" /&gt; &lt;/baseAddresses&gt; &lt;/host&gt; &lt;/service&gt; &lt;/services&gt; &lt;behaviors&gt; &lt;serviceBehaviors&gt; &lt;behavior name="ABCServiceBehavior"&gt; &lt;serviceMetadata httpGetEnabled="false" /&gt; &lt;serviceDebug includeExceptionDetailInFaults="true" /&gt; &lt;/behavior&gt; &lt;/serviceBehaviors&gt; &lt;/behaviors&gt; &lt;/system.serviceModel&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USakif
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMultiple Base Addresses and Multiple Endpoints in WCF
      1. USGrzegorz
      1. VTFavorite
    2. VO
      singulars
      1. POMultiple Base Addresses and Multiple Endpoints in WCF
      1. USsantosh singh
      1. VTFavorite
    3. VO
      singulars
      1. POMultiple Base Addresses and Multiple Endpoints in WCF
      1. This table or related slice is empty.
      1. VTUpMod
    1. COQuick question, why do you want to separate the tcp and http endpoints mex wise?
      singulars
      1. POMultiple Base Addresses and Multiple Endpoints in WCF
      1. USMikael Svenson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload