Type Profile

It has a single method - create profile. This is used to map interfaces to concrete types (this is a fundamental concept in dependency injection - take a look at structure map for more information).

The type profile is the main place to override default implementations. For example, if there is a content type that you want to use an alternate data service, you'd use the type profile to tie that content type to the alternate data source.

It doesn't directly contribute to pushing data to the data source (which makes it different from pretty much every other component of SLAM). Rather, it provides the hooks into the SLAM architecture for override default behavior.

Last edited Jan 23, 2009 at 10:23 PM by AWSystems, version 1


No comments yet.