IoC containers and service locator pattern
I am trying to get an understanding of Inversion of Control and the dos and donts of this. Of all the articles I read, there is one by Mark Seemann (which is widely linked to in SO) which strongly asks folks not to use the service locator pattern.
Desktop application, dependency injection
I am thinking of applying a real dependency injection library to my toy C#/GTK# desktop application. I chose NInject, but I think this is irrelevant to my question.
Refactoring expansive message architecture
I am currently working with a system that acts like a message bus. A message comes in to the service (WCF Windows Service hosted). The system then uses a service locator pattern to look up which dynamically loaded assembly will be assigned to the message. The assembly is found and then a method is executed which handles the message. The response is then sent back to the client.
What is a Service Locator?
I’ve heard the term pop all around. I’ve read various articles regarding the subject and heard two main definitions to the term “Service Location”:
How should dependencies be managed across a modular application?
Let’s say that we have a structure like this:
How should dependencies be managed across a modular application?
Let’s say that we have a structure like this:
API design with references to root object
[Normally I post on StackOverflow but as this is more a design/theory question rather than a code question I’ll give it a shot here]
API design with references to root object
[Normally I post on StackOverflow but as this is more a design/theory question rather than a code question I’ll give it a shot here]
How to decouple simple factory and default implementation?
I have a simple factory class (FileResources
) with static factory methods providing a default implementation (DefaultFileResource
).
How to decouple simple factory and default implementation?
I have a simple factory class (FileResources
) with static factory methods providing a default implementation (DefaultFileResource
).