<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Eventing on Andy Bulka</title>
		<link>https://abulka.github.io/tags/eventing/</link>
		<description>Recent content in Eventing on Andy Bulka</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 02 Nov 2026 16:05:57 +1100</lastBuildDate>
		
			<atom:link href="https://abulka.github.io/tags/eventing/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>HexMVC Eventing</title>
				<link>https://abulka.github.io/patterns/hexmvc-eventing/</link>
				<pubDate>Sat, 12 Feb 2022 00:00:00 +0000</pubDate>
				<guid>https://abulka.github.io/patterns/hexmvc-eventing/</guid>
				<description>&lt;p&gt;Andy Bulka,&lt;br&gt;&#xA;March 2012&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://abulka.github.io/patterns/hexmvc/#appendix&#34;&gt;Back&lt;/a&gt; to main HexMVC Pattern.&lt;/p&gt;&#xA;&lt;h2 id=&#34;on-eventing&#34;&gt;On Eventing&lt;/h2&gt;&#xA;&lt;p&gt;Eventing is up to you to implement any way you like. You need to be able to broadcast &amp;rsquo;events&amp;rsquo; which cause methods to be run on an arbitrary number of observers. The broadcaster is ignorant of the exact identity of the observers. Its the observer pattern.&lt;/p&gt;&#xA;&lt;h3 id=&#34;a-lightweight-synchronous-eventing-system&#34;&gt;A lightweight synchronous eventing system&lt;/h3&gt;&#xA;&lt;p&gt;I recommend a lightweight synchronous eventing system / observer pattern that is based on method calling on objects. It&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
