StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I don't completely understand what's bugging you here, but I would like to respond with a few thoughts/facts:</p> <ol> <li><p>When using SOAP bindings (<code>basicHttpBinding</code>, <code>wsHttpBinding</code>), all you're "exposing" is the endpoint of the service; when hosting in IIS (which seems the case here) this would be a <code>*.svc</code> file that needs to exist somewhere in your IIS folder structures. That svc file then basically contains all the logic you're asking for, that describes what <code>ServiceHost</code> to create to handle the request etc., and the SOAP message contains the information about what method to call and what parameters to pass in. </p></li> <li><p>When using REST (<code>webHttpBinding</code>), the basic premise and basic "way of functioning" of REST dictates that you expose everything as a resource that can be accessed using an URI - so it is the basic assumption of REST that you <strong>do</strong> expose your service "methods" - since those aren't methods, really, but resources you can work with</p></li> </ol> <blockquote> <p><em>Do some trivial parsing against the URL string, then the server will know the Binding protocol and Address, (this is the A and B part of the aforementioned ABC).</em></p> </blockquote> <p>The <strong>address</strong> part of the ABC of WCF seems pretty clear: whatever you type in or whatever your client uses as the target URL is the address of the service you're calling to.</p> <p>The <strong>binding</strong> is also pretty much a given since you have to prefix your URI with a protocol moniker - http, net.tcp, net.msmq and so forth</p> <p>This leaves the <strong>contract</strong> which is defined by the *.svc file when hosting in IIS - the svc file defines what <code>ServiceHostFactory</code> to use to create a <code>ServiceHost</code> to handle the request; I don't really see how else you want to have this happen, and to me, an svc file is almost a bit like a config file anyway.</p> <p>So what exactly are you expecting from "trivial parsing" in terms of figuring out the ABC of WCF ?? Can you explain a bit more? Maybe show a hypothetical sample?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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