Slide 1 : A Web Service is programmable application logic accessible via standard Web protocols. One of these Web protocols is the Simple Object Access Protocol (SOAP). SOAP is a W3C submitted note that uses standards based technologies (XML for data description and HTTP for transport) to encode and transmit application data. Consumers of a Web Service do not need to know anything about the platform, object model, or programming language used to implement the service; they only need to understand how to send and receive SOAP messages (HTTP and XML). Web Services Unleashed
Slide 2 : Definition at it’s core: A service is some functionality that is exposed via a structured messaging scheme.
This functionality can be shared over any transport medium like HTTP, TCP/IP.
A structured messaging scheme can be something like what is defined in HTTP, where you have a request and a reply
Or REST where you can add extra headers in order to add information to request or response objects.
Or it could also be SOAP centric where we add SOAP headers.
Slide 3 : Sockets- Root level, use it when you need high end customizable applications.
Http Listener-Better than sockets but again all security, access control is to be implemented by the user.
ASP.NET- Still lacks support for serialization and de-serialization.
ASMX- Good for building basic http services, they are SOAP centric. Problems with .asmx being, they couldn’t be used with other hosts and applications(other than IIS )
WCF The Evolution Of Web Services using .NET Framework.
Slide 4 : EVIDENCE:
All server products that Microsoft offers use WCF
ADO.NET Data Services uses WCF
SQL Server Data Services uses WCF as well.
FEATURES:
Debugging support
WCF is for both Web and Enterprise applications.
Runs in Trusted Security level, doesn’t requires ownership of web server. The Future
Windows Communication Foundation