Re: Pattern Question

russel,

currently i m not having the book, but from your expression for the
plug-in , i didnt understand ur query ?


what you have described (plugin) is very simillar to "Programming to
Interface--not to implementation" and LSP


Registry somewhat imples that you are accessing existing instances of
types. If we are mainly building new instances does that violate that
pattern too.




I think if you are building new instances of *same type* then it
should not be the problem, But Beware, I am yet not sure (from ur
description), (this is also like Prog to I'face,LSP --I think registry
is more than these...)


--raxit

russell@xxxxxxxxxxxxx wrote:
I am having a discussion with someone in my office about two patterns.


plug-in and registry.

What we are building is a global definition of what type to use in a
particular implementation. This makes it sound like a good match to
plug-in but here is my problem. The way we are doing it allows for the
particular implementations to inherit from each other. In fact core
product types can be replaced via this definition for a particular
implmentation.

My concern with plug-in is that it in the Patterns book I am using
(Martin Fowler's Patterns of Enterprise Application Architecture) talks
about a plug-in pattern as Linking types at configuration time not
compile time. What we are doing does not support the abstraction of
no compile time linking. Is that big enough to though it out of the
pattern?

Registry somewhat imples that you are accessing existing instances of
types. If we are mainly building new instances does that violate that
pattern too.

What you would call the application component defined above?

.

Relevant Pages

  • Re: Pattern Question
    ... The discussion of the plug-in vs registry is a step high on the ... Registry pattern doesn't have the same issue about compile time linking ...
    (comp.object)
  • Re: Pattern Question
    ... like very simple abstraction. ... you want to decide at compile time, or at best, at run ... That sounds like the Factory Method pattern. ... plug-in but here is my problem. ...
    (comp.object)
  • Re: Pattern Question
    ... The discussion of the plug-in vs registry is a step high on the ... the Dependency Injection pattern and the Service Locator pattern. ... particular interface but may be sub-class of the requested type. ...
    (comp.object)
  • Re: Pattern Question
    ... The discussion of the plug-in vs registry is a step high on the ... Meaning it contains a builder and a number of other components. ... Registry pattern doesn't have the same issue about compile time linking ...
    (comp.object)
  • Re: mscoree.dll creating new appdomain with local configuration
    ... host application to find the new plug-in, I have to write some bits into ... ConfigFile entry in the registry and does create a new AppDomain with the ... configured the way I wanted it was to use the "hosting" API. ...
    (microsoft.public.dotnet.framework.interop)