Difference between revisions of "COSMOS Design 197521"

Revision as of 14:13, 5 September 2007

Design Discussion for 197521: component implementation - separating framework vs. extension code

Separation of Concerns for COSMOS DC framework

This design document addresses COSMOS Bugzilla enhancement request 197521.

Change History:

Joel Hawkins 9/05/2007 Initial version

Overview

Current situation - using java stack as mechanism for managing component invocation. Threading issues delegated to components.

Implementation Stages and Corporate Use Cases

Terminologies/Acronyms

The terminologies/acronyms below are commonly used throughout this document. The list below defines each term:

COMPONENT: component definition

BINDING SERVICE: binding service definition

CONTEXT: context definition

Use Cases

Use Case 1. Simple Collection Scenario

A Broker invokes the "registration" operation of the Management Domain, providing the following information:

• EPR for the Broker
• Name of the Broker
• Classification or Type of the Broker (Data or Service)

Management Domain populates its internal registry with the information about the Broker

Management Domain changes the state of the Broker to online and updates the timestamp

If the Broker is already registered with the Management Domain, the Broker invokes the "ping" operation, which updates the timestamp in the Management Domain registry

Use Case 2. Simple Query Scenario

• A Broker invokes the deregister operation of the Management Domain, providing the Broker name as a parameter.
• the Management Domain removes the registration entry for the Broker from its internal registry.

External Interfaces

Framework Interface

Include code snippet

Component Interfaces

Include code snippets

Conventions

Naming expectations used by reflection during compilation.

Framework Implementation Details

Discussion of compilation steps and runtime interactions

Notes