<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wcf on ZBrad's Blog</title><link>https://zbrad.github.io/tags/wcf/</link><description>Recent content in Wcf on ZBrad's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 28 Jul 2016 00:00:00 -0700</lastBuildDate><atom:link href="https://zbrad.github.io/tags/wcf/feed.xml" rel="self" type="application/rss+xml"/><item><title>Websockets in Asp.Net Core</title><link>https://zbrad.github.io/tools/wscore/</link><pubDate>Thu, 28 Jul 2016 00:00:00 -0700</pubDate><guid>https://zbrad.github.io/tools/wscore/</guid><description>&lt;p&gt;An example of creating and using a WebSocket with the new ASP.NET Core. The example code is available on GitHub &lt;a href="https://github.com/zbrad/wsweb"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h1 id="background"&gt;Background&lt;/h1&gt;
&lt;p&gt;WebSockets were introduced as part of the draft HTML5 specification in 2008, and the first browser to provide support was Google Chrome in 2009.&lt;/p&gt;
&lt;p&gt;At this time (July 2016), the following browsers fully support the WebSocket
standard (&lt;a href="https://tools.ietf.org/html/rfc6455"&gt;RFC 6455&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Internet Explorer 10&lt;/li&gt;
&lt;li&gt;Firefox 11 (PC,Android)&lt;/li&gt;
&lt;li&gt;Chrome 16 (PC,Mobile)&lt;/li&gt;
&lt;li&gt;Safari 6 (Mac,iOS)&lt;/li&gt;
&lt;li&gt;Opera 12.10 (PC,Mobile)&lt;/li&gt;
&lt;li&gt;Android Browser 4.4&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="websockets"&gt;Websockets&lt;/h2&gt;
&lt;p&gt;Unlike the HTTP protocol, a WebSocket provides fully bi-directional (full-duplex) communication, enabling a event based
model of programming using a message passing protocol. Since there is not the constant overhead of re-establishing the connection, the
passing of multiple small messages is extremely efficient and lends itself well to client/service interactions
with low latency.&lt;/p&gt;</description></item><item><title>WcfLib - WCF services, clients, and routers</title><link>https://zbrad.github.io/tools/WcfLib/</link><pubDate>Mon, 19 Oct 2015 00:00:00 -0700</pubDate><guid>https://zbrad.github.io/tools/WcfLib/</guid><description>&lt;p&gt;Describes the &lt;a href="https://github.com/zbrad/WcfLib"&gt;WcfLib&lt;/a&gt; component, for easily creating Wcf services, clients, and routers. These are useful for creating and communicating with WCF services, particularly in Azure environments which require WCF routing capabilities. Available as a (&lt;a href="https://www.nuget.org/packages/ZBrad.WcfLib/"&gt;WcfLib NuGet Library&lt;/a&gt;)&lt;/p&gt;
&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve been working with a customer who was looking to re-host one of their existing applications in the &lt;a href="https://azure.microsoft.com/en-us/campaigns/service-fabric/"&gt;Microsoft Azure Service Fabric&lt;/a&gt; environment.&lt;/p&gt;
&lt;p&gt;This particular application uses &lt;a href="https://msdn.microsoft.com/en-us/library/ms731082(v=vs.110).aspx"&gt;Windows Communication Foundation (WCF)&lt;/a&gt; framework for communication between clients and services. However when hosting applications in Azure Service Fabric, clients typically do not directly connect to services, but utilize a router or gateway to talk to
the services (see next article on a Fabric router).&lt;/p&gt;</description></item></channel></rss>