Intro
Time to move on for new ambitious project has come to the front so I just flipped open my laptop computer and started to tip and tap keyboard searching and exploring C++ world.The first of all server side system should be set up. WCF is aka primary solution for establishing Communication using web services on Windows platform but for my project WWSAPI(Windows Web Service API) would be the one to serve all data to native code app.
The main idea behind creating the Windows Web Services API (WWSAPI) was to offer a solution to developers that need to run a web service but could not depend on WCF for a particular reason. Some technologies such as the SOAP toolkit offered this functionality, but they haven’t been updated in a while to conform to the latest protocols, specifications, and standards. With WWSAPI, web services can be written with the Win32 API and they have absolutely no dependency on the .Net framework.
-
Connecting native code and web services
- Win32 API
- No dependency on .Net Framework
-
Interoperability with WS- *SOAP stacks
- Windows Communiation Foundation(WCF)
- ASP .Net XML Web Services (ASMX)
- Non-Microsoft stacks
-
System Component of Windows 7
- Available for Windows XP/Vista/2003/2008
Architecture and Principles
Windows Web Services is a layered API and it may be pictured as the picture above. Every layer exposes a set of APIs and types that can be used with APIs of that layer.
The top-level layer called the Service Model provides a method-based programming model and it is the easiest model to use. In the Service Model, the Service Host provides the server side-programming model, while the Service Proxy provides the client side programming model. Context is used within the Service Model to pass in a relevant state available to the service operation and/or the callback when it is invoked. And Service Contract is used in specify a service contract on an endpoint exposed on the service.
The Service Model is built upon a Channel Layer, which provides full flexibility but is more difficult to use. The Channel Layer is in turn built upon a lightweight XML framework, which includes Serialization of C data types.
The XML layer exposes you to the formatting of messages and serialization of data. You have full access to the content of messages but are shielded from the particular encoding whether you’re communicating with text, binary or MTOM.
Apart from the functions and data structures that logically belong to these three layers, the WWS API provides a number of facilities that are common to all layers, including error handling, asynchronous completion, cancellation, memory management and more. Because I have limited space and want to help you get started quickly, I’m going to limit the rest of this article to the use of the service model for building a Web service client and server.
The following topics are the one I will go thorough from now on.
Comments
Post a Comment