----- Original Message -----
From: "Berin Loritsch" <[EMAIL PROTECTED]>
> > Agree. This list should be done by Berin while he have the big picture.
>
> First, let's talk a little about strategy.
>
<...>
>
> Merlin represents a different way of doing things (if I understand it
> correctly), in that it has a generic Appliance interface. The Appliance
> interface is the generic do-all interface that can be adapted many ways.
I don't know how Appliance interface works but I see a fine design in
Asp.net Modules handling. Basicly IHttpModule is:
public interface IHttpModule
{
void Init(HttpApplication app)
void Dispose()
}
The module implements Init as
public void Init(HttpApplication app)
{
// subscribe for interesting events....
}
So a Module can participate in the entire lifecycle of a page (aspx, asmx
etc).
Examples of Modules are SessionStateModule, AuthorizationModule,
ContentsCacheModule - very different modules that listen to very diferents
events.
This is a example of using a generic approach that could be useful for
lifecycle management but I don't think it fit in ComponentFactory. Also this
approach is nice for extensions (maybe I'm seeing far ahead)....
> * The ability to create and instantiate a component.
> * The ability to destroy a component.
> * Assemble components (provide a mapping functionality).
Could you explain more of this last one? Or are you just talking about
resources et al?
hammett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
