Container - Container-Component Architectures...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Container-Component Architectures Container-Component Architectures are examples of open architectures because they allow users to extend an application's functionality by adding new components created by third party developers. Components have to be added without modifying the code of the original application since users don't have access to the application's source code. The Container-Component Architecture is a good example of the Open-Closed Principle . A component (also called a plugin) consists of one or more collaborating objects, implements some interfaces, and requires interfaces to be implemented. The detailed definition of a component can be found here . Components provide system functionality. The container's job is to manage the lifecycle of its components (create, suspend, resume, destroy) and also to provide infrastructure services to the components such as communication, persistence, security, execution environment (a VM for example), synchronization, white and yellow page directories, etc. Examples of applications that follow the Container-Component Architecture include:
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/21/2009 for the course CS 267 taught by Professor Butt,f during the Fall '08 term at San Jose State.

Page1 / 2

Container - Container-Component Architectures...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online