endpoints

I was under the impression that an endpoint was defined in a config file as the list of possible clients but that makes no sense (in the sense that I assumed it said what computers could connet to the service) now I'm gathering that it's more of a definition, so would someone please explain what an end point is to me? I understand the concept of definining the contract interface and then implementing the contract but I get lost somewhere between there and actually having something useable. What is an address in this context? the host address? A binding is the communications method/protocol to

Will it consume from all of them? Will it throw an exception? You can have multiple endpoints for the same contract and different addresses in your clieint config, no problem. They need to be separated by a unique name= attribute on the <endpoint> tag. <client> <endpoint name="tcpEndpoint" address="net.tcp://server:8888/SomeService" binding="netTcpBinding" contract="IYourService" /> <endpoint name="httpEndpoint" address="http://server:8777/SomeService" binding="basicHttpBinding" contract="IYourService" /> </client> When you create your client proxy, you need to provide the name of the endpoint

I'm currently using SendGrid's Inbound Parse Webhook to feed emails to my application. I've been able to get it working by pointing the URL to an endpoint which my application has exposed. SendGrid just sends the email in the form of a JSON format HTTP POST request to this endpoint and I just process each request internally. My question is, now that I have it working, how do I ensure that only SendGrid can use this endpoint? At the moment, anyone can utilise this HTTP POST endpoint and pretend that an email has been sent to the application. Can I get SendGrid to send some sort of unique key to

How can I code a c# sample for reading my Client endpoint configurations: <client> <endpoint address="http://mycoolserver/FinancialService.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IFinancialService" contract="IFinancialService" name="WSHttpBinding_IFinancialService"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="http://mycoolserver/HumanResourcesService.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IHumanResourceService" contract="IHumanResourceService" name="WSHttpBinding_IHumanResourceService"> <identity> <dns value

I've got an assembly containing several WCF services, each with its own contract. It all works nicely. The service config in the app.config for the service looks like this: <services> <service behaviorConfiguration="WcfService.AlyzaServiceBehavior" name="Sam.Alyza.WcfService.ServiceWebsites"> <endpoint address="" binding="netTcpBinding" contract="Sam.Alyza.WcfInterface.IServiceWebsites"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="mex" binding="mexTcpBinding" contract="IMetadataExchange" /> <host> <baseAddresses> <add baseAddress="net.tcp://localhost:8731

What I am trying to do is get a SINGLE WCF Service to work in the development environment which is the HTTP scheme, and, also, have the SAME service work in the production environment which is the HTTPS scheme. If I remove the two Https endpoints (those suffixed 'Https'), it works in the development enviornment; likewise, if I remove only the two Http endpoints then it works in the production environment. I would like to have all four endpoints in the web.config, if possible. My endpoints are defined below: <endpoint address="/Web" behaviorConfiguration="AjaxBehavior" binding="wsHttpBinding"

I have been trying to add a new endpoint in a service hosted under IIS but haven't been able to figure it out for the past day or so. This is my understanding: you can have multiple endpoints under IIS as long as they have unique addresses. you could assign a base address but it will be overridden by the virtual directory setup in IIS. My virtual directory is http://localhost/WcfCert/ <services> <service name="WcfCertServer.Service1" behaviorConfiguration="WcfCertServer.Service1Behavior"> <endpoint address="" binding="wsHttpBinding" contract="WcfCertServer.IService1"/> <endpoint address="test"