<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Adapter on Andy Bulka</title>
		<link>https://abulka.github.io/tags/adapter/</link>
		<description>Recent content in Adapter 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/adapter/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>HexMVC Adapters</title>
				<link>https://abulka.github.io/patterns/hexmvc-adapters/</link>
				<pubDate>Sat, 12 Feb 2022 00:00:00 +0000</pubDate>
				<guid>https://abulka.github.io/patterns/hexmvc-adapters/</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;adapter-design-patterns&#34;&gt;Adapter Design Patterns&lt;/h2&gt;&#xA;&lt;p&gt;In HexMvc the adapter implementing interfaces is everywhere. What pattern is this? Obviously Adapter Pattern is a leading candidate.&lt;/p&gt;&#xA;&lt;h3 id=&#34;talking-to-interfaces-vs-adapter-pattern&#34;&gt;Talking to Interfaces vs Adapter Pattern&lt;/h3&gt;&#xA;&lt;p&gt;You could just call it the talking to Interfaces pattern. As GOF says in its introduction, one of the main two OO principles is &amp;ldquo;Program to an interface, not an implementation&amp;rdquo; (&lt;a href=&#34;http://en.wikipedia.org/wiki/Design_Patterns&#34;&gt;Gang of Four&lt;/a&gt; 1995:18). This allows clients to be decoupled from the implementation.&lt;/p&gt;</description>
			</item>
			<item>
				<title>HexMVC Scraps</title>
				<link>https://abulka.github.io/patterns/hexmvc-scraps/</link>
				<pubDate>Sat, 12 Feb 2022 00:00:00 +0000</pubDate>
				<guid>https://abulka.github.io/patterns/hexmvc-scraps/</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;h3 id=&#34;renamings-of-puremvc-terms-to-adapter&#34;&gt;Renamings of pureMvc terms to &amp;ldquo;Adapter&amp;rdquo;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;PureMvc uses the term one or more &amp;ldquo;mediators&amp;rdquo; in front of gui plumbing - all sitting behind the term &amp;ldquo;View&amp;rdquo;&lt;/li&gt;&#xA;&lt;li&gt;PureMvc uses the term one or more &amp;ldquo;proxies&amp;rdquo; in front of model plumbing - all sitting behind the term &amp;ldquo;Model&amp;rdquo;&lt;/li&gt;&#xA;&lt;li&gt;PureMvc talks about many &amp;ldquo;commands&amp;rdquo; objects which all sit behind the term &amp;ldquo;Controller&amp;rdquo;&lt;/li&gt;&#xA;&lt;li&gt;The Application &amp;ldquo;facade&amp;rdquo; is the centre.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The problem with these terms are that is debatable that these things are really proxies and mediators etc. I rename them Adapters.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
