<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Life of RubenV (Ruben Vermeersch) &#187; erlang</title>
	<atom:link href="http://weblog.savanne.be/tags/erlang/feed" rel="self" type="application/rss+xml" />
	<link>http://weblog.savanne.be</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 14:14:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Actor Model</title>
		<link>http://weblog.savanne.be/155-the-actor-model</link>
		<comments>http://weblog.savanne.be/155-the-actor-model#comments</comments>
		<pubDate>Mon, 12 Jan 2009 13:09:02 +0000</pubDate>
		<dc:creator>Ruben</dc:creator>
				<category><![CDATA[concurrency]]></category>
		<category><![CDATA[erlang]]></category>
		<category><![CDATA[scala]]></category>

		<guid isPermaLink="false">http://weblog.savanne.be/155-the-actor-model</guid>
		<description><![CDATA[<p>When you have to do things concurrently in an application, the first thing that comes to mind is usually: &#8220;I&#8217;ll use a thread!&#8221;. Usually, if you&#8217;re lucky enough, this is followed by: &#8220;But threads are a pain&#8230;&#8221;.</p>
<p>I recently studied an interesting alternative at the university: the Actor Model. This model provides a manageable alternative to threads and locking. The prime example of an actor model implementation is <a href="http://www.erlang.org">Erlang</a>, which is getting very popular these days.</p>
<p>Anyway, as part of this course, I wrote a paper discussing the concurrency in Erlang and Scala (which also uses the actor model). If you&#8217;ve ever fought with threads and wished there would be an alternative, this might be interesting for you:</p>
<p><a href="http://ruben.savanne.be/articles/concurrency-in-erlang-scala">Concurrency in Erlang and Scala: The Actor Model</a></p>
<p>Related and also interesting are the <a href="http://prog.vub.ac.be/~tvcutsem/teaching/csse/">slides of this course</a>, which also discuss communicating event loops (similar to the GLib events).</p>
]]></description>
			<content:encoded><![CDATA[<p>When you have to do things concurrently in an application, the first thing that comes to mind is usually: &#8220;I&#8217;ll use a thread!&#8221;. Usually, if you&#8217;re lucky enough, this is followed by: &#8220;But threads are a pain&#8230;&#8221;.</p>
<p>I recently studied an interesting alternative at the university: the Actor Model. This model provides a manageable alternative to threads and locking. The prime example of an actor model implementation is <a href="http://www.erlang.org">Erlang</a>, which is getting very popular these days.</p>
<p>Anyway, as part of this course, I wrote a paper discussing the concurrency in Erlang and Scala (which also uses the actor model). If you&#8217;ve ever fought with threads and wished there would be an alternative, this might be interesting for you:</p>
<p><a href="http://ruben.savanne.be/articles/concurrency-in-erlang-scala">Concurrency in Erlang and Scala: The Actor Model</a></p>
<p>Related and also interesting are the <a href="http://prog.vub.ac.be/~tvcutsem/teaching/csse/">slides of this course</a>, which also discuss communicating event loops (similar to the GLib events).</p>
]]></content:encoded>
			<wfw:commentRss>http://weblog.savanne.be/155-the-actor-model/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

