architecture_styles
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
architecture_styles [2015/02/28 09:56] apaschke [Direct Strongly-Coupled API4KB Access] |
architecture_styles [2015/02/28 09:56] apaschke [Distributed Components] |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| A unit of composition with contractually specified interfaces and explicit content dependencies only. Component is specified in terms of a contract which includes a set of provided interfaces (interfaces that the component offers as a service to other components) and required interfaces (dependencies that this component has on other components). Container provides managed server-side hosting environment for components and deals with the distributed systems and middleware issues. | A unit of composition with contractually specified interfaces and explicit content dependencies only. Component is specified in terms of a contract which includes a set of provided interfaces (interfaces that the component offers as a service to other components) and required interfaces (dependencies that this component has on other components). Container provides managed server-side hosting environment for components and deals with the distributed systems and middleware issues. | ||
| - | Examples, e.g. Java Beans, Corba Component Model, API4KB OntoMaven Aspect-Oriented Component Model, ... | + | Examples, e.g. Java Beans, Corba Component Model, [[http://www.corporate-semantic-web.de/ontomaven.html|OntoMaven Aspect-Oriented Component Model]], ... |
| ===== Decoupled Indirect Communication ===== | ===== Decoupled Indirect Communication ===== | ||
architecture_styles.txt ยท Last modified: 2015/04/24 10:11 by rmbell
Page Tools
