Scribd
Upload
80 views3 pages

WCF Difference FAQs-1

The document compares basicHttpBinding and wsHttpBinding in WCF. BasicHttpBinding supports older .NET versions and a wider range of clients but does not support WS-* specifications. WsHttpBinding exposes services using WS-* specifications, supports reliable messaging and security features like message credentials and transport security, but may not be consumed by very old .NET versions. It also discusses the differences between message level and transport level security in WCF.

Uploaded by

Umar Ali
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
80 views3 pages

WCF Difference FAQs-1

The document compares basicHttpBinding and wsHttpBinding in WCF. BasicHttpBinding supports older .NET versions and a wider range of clients but does not support WS-* specifications. WsHttpBinding exposes services using WS-* specifications, supports reliable messaging and security features like message credentials and transport security, but may not be consumed by very old .NET versions. It also discusses the differences between message level and transport level security in WCF.

Uploaded by

Umar Ali
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Difference between basicHttpBinding and wsHttpBinding Criteria BasicHttpBinding WsHttpBinding This exposes web services using WS-* specifications.

As its built using WS-* specifications, it does not support wider ranges of client and it cannot be consumed by older .NET version less than 3 version.

Security This supports the old ASMX style, i.e. WS-BasicProfile 1.1. support Compatibility This is aimed for clients who do not have .NET 3.0 installed and it supports wider ranges of clients. Many of the clients like Windows 2000 still do not run .NET 3.0. So older version of .NET can consume this service. Soap version SOAP 1.1 Reliable messaging Not supported. In other words, if a client fires two or three calls you really do not know if they will return back in the same order. By default, there is no security provided for messages when the client calls happen. In other words, data is sent as plain text. None Windows default authentication Basic Certificate

SOAP 1.2 and WS-Addressing specification. Supported as it supports WS-* specifications.

Default security options Security options

As WsHttBinding supports WS-*, it has WS-Security enabled by default. So the data is not sent in plain text. None Transport Message Transport with message credentials

Difference between Message and Transport level security in WCF Criteria Scenarios when we should be using one of them Transport Security When there are no intermediate systems in between this is the best methodology. Message Security

When there are intermediate systems like one more WCF service through which message is routed then message security is If its an intranet type of solution the way to go. this is most recommended methodology. Does not need any extra coding as protocol inherent security is used. Performance is better as we can use hardware accelerators to enhance performance. There is lot of interoperability support and communicating Provides end to end security as its not dependent on protocol. Any intermediate hop in network does not affect the application. Supports wide set of security options as it is not dependent on protocol. We can also implement custom security.

Advantages

clients do not need to understand WS security as its built in the protocol itself. Disadvantages As its a protocol implemented Needs application refactoring to security so it works only point to implement security. point. As every message is encrypted As security is dependent on and signed there are performance protocol it has limited security issues. support and is bounded to the protocol security limitations. Does not support interoperability with old ASMX webservices

Difference between Buffered transfer and Streamed transfer in WCF S.No 1 2 3 Buffered Transfer Target can process the message once it is completely received. Performance will be good when message size is small Native channel shape is IDuplexSessionChannel Streamed Transfer Target can start processing the data when it is partially received. Performance will be good when message size is larger(more than 64K) Native channels are IRequestChannel and IReplyChannel

Difference between WCF and Web Services S.No 1 Features Hosting WebService It can be hosted in IIS WCF t can be hosted in IIS, windows activation service, Self-hosting, Windows service [ServiceContract] attribute has to be added to the class [OperationContract] attribute represents the method exposed to client One-Way, RequestResponse, Duplex are different type of operations supported in WCF System.Runtime.Seriali zation namespace is used for serialization XML 1.0, MTOM, Binary, Custom

2 3

Programming Model

[WebService] attribute has to be added to the class [WebMethod] attribute represents the method exposed to client One-way, RequestResponse are the different operations supported in web service System.Xml.serialization name space is used for serialization XML 1.0, MTOM(Message Transmission Optimization Mechanism), DIME, Custom

Operation

5 6

XML Encoding

Transports

Can be accessed through HTTP, TCP, Custom Security Web Services are stateless

8 9

Protocols State Management

Can be accessed through HTTP, TCP, Named pipes, MSMQ,P2P, Custom Security, Reliable messaging, Transactions WCF Services can manage states

You might also like