﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Marek Dec commented on Design patterns in the test of time: Bridge</title><description>Your example is somehow wrong. Actually the only Interface here is the one called CImageImp. Why does it have the Imp suffix then? Actually the CImageImp makes me think that it's an implementation of the CImage (which is not obviously not true given the uml notation you used). Then CImage cannot be a pure interface (as somebody suggests here) as it "has" a CImageImp. The quality of the wikipedia article you linked here is much better, I'd say that you read it once again and refine yours.</description><link>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment5</link><guid>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment5</guid><pubDate>Wed, 21 Nov 2012 08:58:45 GMT</pubDate></item><item><title>Kyle Szklenski commented on Design patterns in the test of time: Bridge</title><description>As the occasional publisher of APIs, I have used and abused the bridge pattern over and over and over. I've used it more in C++ than in .NET, but it can be useful there, too, at times.</description><link>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment4</link><guid>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment4</guid><pubDate>Mon, 05 Nov 2012 16:41:25 GMT</pubDate></item><item><title>Niels Krijger commented on Design patterns in the test of time: Bridge</title><description>I've seen this pattern used only used once or twice explicitly; that is, being named "Bridge". However, this pattern -like most others frankly- grow into existence somehow, particularly when you're really set for decoupling two bodies of code.

I regularly have a model project (which I can understand) implemented by a specific technology (which I don't, but with some gOOgling fiddle out in the end). I don't want the difficult technology ruin my simple view of the world (that is, I don't want technology X mess up my model). I think most who are fully dedicated to their models won't let their implementation leak into their model. Henceforth, the Bridge is created; even though the programmer has no idea what is actually is. That is why you hardly ever see it in the real world; it is often decoupled so much you don't even notice.</description><link>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment3</link><guid>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment3</guid><pubDate>Fri, 02 Nov 2012 23:53:26 GMT</pubDate></item><item><title>Niv Eliyahu commented on Design patterns in the test of time: Bridge</title><description>The bridge pattern come to solve problems that ioc/di solves, the bridge is the oldest way.</description><link>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment2</link><guid>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment2</guid><pubDate>Fri, 02 Nov 2012 17:23:10 GMT</pubDate></item><item><title>Arnon Rotem-Gal-Oz commented on Design patterns in the test of time: Bridge</title><description>You actually see this quite a lot - only what's shown here on the CImage side all have I prefixes (in .NET)  i.e. they are all interfaces... </description><link>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment1</link><guid>http://ayende.com/159489/design-patterns-in-the-test-of-time-bridge#comment1</guid><pubDate>Fri, 02 Nov 2012 12:01:04 GMT</pubDate></item></channel></rss>