Comments on: Real World Benefits From Loose Coupling, Inversion Of Control And Dependency Injection

By: Why You Don’t Need Dependency Injection In Ruby | The Inquisitive Coder – Davy Brion's Blog

Mon, 11 Oct 2010 06:02:30 +0000

[...] Lowered coupling between classes which enables you to change implementations of dependencies at will (granted, not a lot of people actually do that often but it certainly is a real benefit) [...]

By: Aaron Fischer

Aaron Fischer — Fri, 11 Dec 2009 17:07:06 +0000

@Davy
Your correct the new Keyword is needed in order to add the wcf attributes.

I don’t mind so much it’s an Interface, and this particular case these two interfaces are really the same.

By: Davy Brion

Davy Brion — Thu, 10 Dec 2009 19:02:33 +0000

@Aaron

doesn’t that mean you have to redefine the already existing methods from IRequestProcessor in IWcfRequestProcessor with the ‘new’ keyword, just to be able to add the WCF attributes to them?

I haven’t looked into the downsides of this because i tend to look for another solution whenever i feel like i need the ‘new’ keyword in either a class or interface definition

By: Aaron Fischer

Aaron Fischer — Thu, 10 Dec 2009 18:46:02 +0000

I have found it helpful to define IWcfRequestProcessor as an extention of IRequestProcessors.

public interface IWcfRequestProcessor : IRequestProcessor

Now I can deal with IRequestProcessor, even if we are using wcf.

By: John Sonmez

John Sonmez — Thu, 10 Dec 2009 14:39:49 +0000

Nice concrete example of non-concrete concept.

By: Reflective Perspective - Chris Alcock » The Morning Brew #495

Reflective Perspective - Chris Alcock » The Morning Brew #495 — Thu, 10 Dec 2009 09:54:45 +0000

[...] Real World Benefits From Loose Coupling, Inversion Of Control And Dependency Injection – Davy Brion looks at some the real benefits of implemeing loosely coupled code using Dependency injection and Inversion of control, illustrating with an example of the benefit he realised with his Agatha Request Response Service Layer project [...]