NewLC - ECom plug-in – in the lights of Strategy Pattern - Comments

Re: ECom plug-in – in the lights of Strategy Pattern

makom — Mon, 01 Sep 2008 09:58:50 +0200

Great article.

Re: ECom plug-in – in the lights of Strategy Pattern

somenath — Thu, 21 Aug 2008 22:48:04 +0200

I think you are absolutely right. The discovery, resolution and loading of the plug-in are part of the framework. However, we can realize the strategy pattern using the ECom framework. In fact implementation of the strategy pattern is the most important application area of any plug-in architecture.I think I should have elaborated more.

Anyway, thank you for clarifying.

Re: ECom plug-in – in the lights of Strategy Pattern

alh — Thu, 21 Aug 2008 15:22:59 +0200

You are very right that ECOM seems an excellent match for, and could be used for implementing the Strategy Pattern, but I think you should not try turn that around and say that ECOM _is_ the strategy pattern.

What ecom is, is exactly what it says it is, a plugin architecture.

One thing ecom has, that isn't needed for the strategy pattern is version control.
The main idea is that you can change/update the plugin implementation independently of the main application.

Its really a structural pattern, and not a behavioral one.

In fact, I'd say that most cases when its used, the closest match is the Facade pattern.

ECom plug-in – in the lights of Strategy Pattern

somenath — Thu, 21 Aug 2008 02:26:49 +0200

When I started understanding ECom architecture of Symbian, I tried to map it with some design pattern from the GoF book. This way I found out that the Strategy Pattern described as one of the Behavioral Patterns is the closest match. Let me share my understanding with you.