WCF> Web service: basicHttpBinding vs netTcpBinding

I am trying to understand the main part of WCF when I came across the following question:

Why use basicHttpBindingover netTcpBindingfor a web service?

Can both of them have a mex endpoint that allows you to easily add both of them through the Add Server Link window without any configuration?

I know that the protocol is HTTPbuilt on top of the protocol TCP, but for me it just looks like HTTP provides a lot of incomplete patterns (performance, etc.).

Can someone explain why you chose one of them for the web service?

+3
source share
1 answer

, ,

: netTcp, WCF WCF .

basicHtpp, "" (asmx) "" (java/rails/pythone) , .

: http://msdn.microsoft.com/en-us/library/ff649887.aspx

http://mohammedatef.wordpress.com/tag/basichttpbinding/

+7

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


All Articles