<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tpl on 7sharp9</title><link>https://7sharp9.github.io/tags/tpl/</link><description>Recent content in Tpl on 7sharp9</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>7sharp9@mail.com (Dave Thomas)</managingEditor><webMaster>7sharp9@mail.com (Dave Thomas)</webMaster><copyright>© 2026 Dave Thomas</copyright><lastBuildDate>Sun, 22 Apr 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://7sharp9.github.io/tags/tpl/index.xml" rel="self" type="application/rss+xml"/><item><title>Back to the Primitive II</title><link>https://7sharp9.github.io/programming/2012-04-22-back-to-the-primitive-ii/</link><pubDate>Sun, 22 Apr 2012 00:00:00 +0000</pubDate><author>7sharp9@mail.com (Dave Thomas)</author><guid>https://7sharp9.github.io/programming/2012-04-22-back-to-the-primitive-ii/</guid><description>&lt;p&gt;In the last post I discussed an asynchronous version of the &lt;code&gt;ManualResetEvent&lt;/code&gt; and as promised this time we will be looking at an
asynchronous version of the &lt;code&gt;AutoResetEvent&lt;/code&gt;. I&amp;rsquo;m using &lt;a href="http://blogs.msdn.com/b/pfxteam/archive/2012/02/11/10266923.aspx" target="_blank" rel="noreferrer"&gt;Stephen Toubs post&lt;/a&gt;
as reference and we will be building a version that is functional in style that maps straight into asynchronous work flows without and conversion
or adaptors.&lt;/p&gt;</description></item><item><title>Back to the Primitive</title><link>https://7sharp9.github.io/programming/2012-04-12-back-to-the-primitive/</link><pubDate>Thu, 12 Apr 2012 00:00:00 +0000</pubDate><author>7sharp9@mail.com (Dave Thomas)</author><guid>https://7sharp9.github.io/programming/2012-04-12-back-to-the-primitive/</guid><description>&lt;p&gt;In this post we are going &lt;strong&gt;back to the primitive&lt;/strong&gt;. No it&amp;rsquo;s not about the same named song by Soulfly, &lt;em&gt;(which incidentally does contains F# notes)&lt;/em&gt; but a return to thread synchronisation primitives and their asynchronous counterparts.&lt;/p&gt;
&lt;p&gt;We are going to be looking at an asynchronous version of the &lt;a href="http://msdn.microsoft.com/en-us/library/system.threading.manualresetevent.aspx" target="_blank" rel="noreferrer"&gt;ManualResetEvent&lt;/a&gt;. This was
recently covered by Stephen Toub on the &lt;a href="http://blogs.msdn.com/b/pfxteam/archive/2012/02/11/10266920.aspx" target="_blank" rel="noreferrer"&gt;pfx team blog&lt;/a&gt;. We will be taking a slightly different view on
this as we will be using asynchronous workflows which will give us nice idiomatic usage within F#.&lt;/p&gt;</description></item><item><title>Pipeline processing 3</title><link>https://7sharp9.github.io/programming/2011-04-04-pipeline-processing-3/</link><pubDate>Mon, 04 Apr 2011 00:00:00 +0000</pubDate><author>7sharp9@mail.com (Dave Thomas)</author><guid>https://7sharp9.github.io/programming/2011-04-04-pipeline-processing-3/</guid><description>&lt;p&gt;Ok so I have been offline for a while now, what with starting a new financial contract in London and not having any broadband access for a while.  I have
been working on something, honest!&lt;/p&gt;
&lt;p&gt;Since the last post I have been reflecting on the pipeline design and it had a distinct object orientated feel to it that I wasnt happy with, so I have
amended the structure of the code and come up with the following which simplifies in some areas and expands in others&amp;hellip;&lt;!-- more --&gt;&lt;/p&gt;</description></item><item><title>Pipeline processing 1</title><link>https://7sharp9.github.io/programming/2011-02-01-pipeline-processing-1/</link><pubDate>Tue, 01 Feb 2011 00:00:00 +0000</pubDate><author>7sharp9@mail.com (Dave Thomas)</author><guid>https://7sharp9.github.io/programming/2011-02-01-pipeline-processing-1/</guid><description>&lt;h3 class="relative group"&gt;Welcome to new series of articles on pipeline processing.
 &lt;div id="welcome-to-new-series-of-articles-on-pipeline-processing" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#welcome-to-new-series-of-articles-on-pipeline-processing" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;p&gt;First up, what&amp;rsquo;s a pipeline?  Well according to &lt;a href="http://en.wikipedia.org/wiki/Pipeline_%28computing%29" target="_blank" rel="noreferrer"&gt;Wikipedia&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;A pipeline is a set of data processing elements connected in series, so that
the output of one element is the input of the next one. The elements of a
pipeline are often executed in parallel or in time-sliced fashion; in that
case, some amount of buffer storage is often inserted between elements.&lt;/p&gt;</description></item></channel></rss>