ws2007HttpBinding :
.NET Framework 3.5 introduces a new binding for Web service interoperability called the ws2007HttpBinding binding.
This binding is similar to the ws2007HttpBinding binding except that it supports the latest WS-* standards available for messaging, security, reliable messaging, and transactions.This type of communication called Advanced web
service communication.
Address format:
http://{hostname}:{port}/{service location} and https://{hostname}:{port}/{service location} Default port number: 80 for http and 443 for https
WCF supports specifications defined by WS-* specifications. WS-* specifications are defined together by Microsoft, IBM, SUN and many other big companies so that they can expose there service through a common protocol.
WCF supports all specifications defined we will understand them one by one.
• Messaging (WS-Addressing):- SOAP is the fundamental protocol for web services. WS Addressing defines some extra additions to SOAP headers, which makes SOAP free from underlying transport protocol. One of the good things about Message transmission is MTOM, also termed as Message Transmission Optimization Mechanism. They optimize transmission format for SOAP messages in XML-Binary formant using XML optimized packaging (XOP). Because the data will sent in binary and optimized format, it will give us huge performance gain.
• Security (WS-Security, WS-Trust, and WS-Secure Conversation): - All the three WS- define authentication, security, data integrity and privacy features for a service.
• Reliability (WS-Reliable Messaging): - This specification ensures end-to-end communication when we want SOAP messages to be traversed back and forth many times.
• Transactions (WS-Coordination and WS-Atomic Transaction): - These two specifications enable transaction with SOAP messages.
• Metadata (WS-Policy and WS-Metadata exchange): - WSDL is a implementation of WS-Metadata Exchange protocol. WS-Policy defines more dynamic features of a service, which cannot be expressed by WSDL.
We have stressed on the WS-* specification as it is a specification which a service has to follow to be compatible with other languages. Because WCF follows WS-* specifications other languages like JAVA , C++ can also exploit features like Messaging , Security , Reliability and transactions written in C# or VB.NET. This is the biggest achievement of WCF to integrate the above features with other languages.
• Messaging (WS-Addressing):- SOAP is the fundamental protocol for web services. WS Addressing defines some extra additions to SOAP headers, which makes SOAP free from underlying transport protocol. One of the good things about Message transmission is MTOM, also termed as Message Transmission Optimization Mechanism. They optimize transmission format for SOAP messages in XML-Binary formant using XML optimized packaging (XOP). Because the data will sent in binary and optimized format, it will give us huge performance gain.
• Security (WS-Security, WS-Trust, and WS-Secure Conversation): - All the three WS- define authentication, security, data integrity and privacy features for a service.
• Reliability (WS-Reliable Messaging): - This specification ensures end-to-end communication when we want SOAP messages to be traversed back and forth many times.
• Transactions (WS-Coordination and WS-Atomic Transaction): - These two specifications enable transaction with SOAP messages.
• Metadata (WS-Policy and WS-Metadata exchange): - WSDL is a implementation of WS-Metadata Exchange protocol. WS-Policy defines more dynamic features of a service, which cannot be expressed by WSDL.
We have stressed on the WS-* specification as it is a specification which a service has to follow to be compatible with other languages. Because WCF follows WS-* specifications other languages like JAVA , C++ can also exploit features like Messaging , Security , Reliability and transactions written in C# or VB.NET. This is the biggest achievement of WCF to integrate the above features with other languages.
ws2007HttpBinding Client Configuration
<client>
<endpoint address="http://localhost/Service1.svc" binding="ws2007HttpBinding" contract="ServiceReference1.IService1"></endpoint></client>
No comments:
Post a Comment
Please Give Your Valuable Comments on this Topic