none
Regarding different type of endpoint is available in wcf RRS feed

  • General discussion

  • i got this url http://msdn.microsoft.com/en-us/library/ee358762%28v=vs.110%29.aspx

    from here i saw lots of different kind of endpoint exist but i was not aware of those and never used it

    <endpoint address="net.tcp://localhost:5555/Calculator" binding="netTcpBinding"
    contract="CalculatorInterFace.ICalculator" name="NetTcpBinding_ICalculator" />

    i understand about endpoint that it will have service address url and contract name & endpoint name just this much.

    here are all different kind of endpoint

    AnnouncementEndpoint
    A standard endpoint that is used by services to send announcement messages.
    DiscoveryEndpoint
    A standard endpoint that is used by services to send discovery messages.
    UdpDiscoveryEndpoint
    A standard endpoint that is pre-configured for discovery operations over a UDP multicast binding.
    UdpAnnouncementEndpoint
    A standard endpoint that is used by services to send announcement messages over a UDP binding.
    DynamicEndpoint
    A standard endpoint that uses WS-Discovery to find the endpoint address dynamically at runtime.
    ServiceMetadataEndpoint
    A standard endpoint for metadata exchange.
    WebHttpEndpoint
    A standard endpoint with a WebHttpBinding binding that automatically adds the WebHttpBehavior behavior
    WebScriptEndpoint
    A standard endpoint with a WebHttpBinding binding that automatically adds the WebScriptEnablingBehavior behavior.
    WebServiceEndpoint
    A standard endpoint with a WebHttpBinding binding.
    WorkflowControlEndpoint
    A standard endpoint that enables you to call control operations on workflow instances.
    WorkflowHostingEndpoint
    A standard endpoint that supports workflow creation and bookmark resumption.
    so how do i know which endpoint i should use and when?also how do i know how the syntax will look like for different type of endpoint. please discuss as much as possible. thanks

    Friday, February 7, 2014 8:48 AM

All replies

  • WCF provides nine built-in bindings:


    1. BasicHttpBinding: Basic web service communication. Exposes
      WCF services as legacy ASMX web services. Used for interoperability. No security
      by default.
    2. WSHttpBinding: Web services with WS-* support. Supports
      transactions and reliable messaging.
    3. WSDualHttpBinding: Web services with duplex contract and
      transaction support.
    4. WSFederationHttpBinding: Web services with federated
      security. Supports transactions.
    5. MsmqIntegrationBinding: Communication directly with MSMQ
      applications. Supports transactions.
    6. NetMsmqBinding: Communication between WCF applications by
      using queuing. Supports transactions.
    7. NetNamedPipeBinding: Communication between WCF applications
      on same computer. Supports duplex contracts and transactions.
    8. NetPeerTcpBinding: Communication between computers across
      peer-to-peer services. Supports duplex contracts.
    9. NetTcpBinding: Communication between WCF applications
      across computers. Supports duplex contracts and transactions.

    Although most bindings will work on scenarios they are not designed for, it's
    a good practice to choose the right binding for a given endpoint.

    Tuesday, February 11, 2014 7:02 AM