<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Native Web Services, Part 1 - Build a WWSAPI Client</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/philpenn/WWSAPIclient/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/477506_100x75.jpg</url>
		<title>Channel 9 - Native Web Services, Part 1 - Build a WWSAPI Client</title>
		<link></link>
	</image>
	<description>
With the Windows Web Services API (WWSAPI), you can connect your C/C&amp;#43;&amp;#43; client applications with web services. You can also create C/C&amp;#43;&amp;#43; server-side web service end-points. WWSAPI is new with Windows 7 (client) and Windows Server 2008 R2 (server). WWSAPI
 is also back-ported to all formally supported versions of Windows (client and server). The WWSAPI runtime library (WebServices.dll) is a native-code implementation of WS-* family of protocols for SOAP based web services.
 
WWSAPI enables several solution scenarios and benefits including: 
1. Implement web services in native C/C&amp;#43;&amp;#43; code on both Windows client and server. C/C&amp;#43;&amp;#43; application developers have often requested this platform technology capability but were previously forced to write their own or interface their native-code solutions
 with managed-code wrappers.  
2. Achieve interoperability with web services implemented using Windows Communication Foundation (WCF), ASP.NET XML Web Services, and even services implemented using non-Microsoft implementations of WS-* libraries. 
3. Construct web services with minimal service startup time and minimal process working-set dependencies. 
4. Use web services implementations in resource-constrained deployment environments.
 
5. Avoid native-management interop scenarios with potentially costly marshalling side-effects. 
This is part 1 of a 2 episode series and focuses upon using WWSAPI from a client application. The example illustrates a client application using WWSAPI to interact with a &amp;quot;Sort Service&amp;quot;.
 
Find sample code and additional technical details at 
MSDN Code Gallery.

See part 2 of this series 
here. 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Thu, 23 May 2013 05:38:26 GMT</pubDate>
	<lastBuildDate>Thu, 23 May 2013 05:38:26 GMT</lastBuildDate>
	<generator>Rev9</generator>
</channel>
</rss>