This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
general architecture java code structure
chris grzegorczyk edited this page Feb 23, 2013
·
2 revisions
What this boils down to is: We have two "kinds" of modules in ./clc/modules:
1. Library code: this code is at the root of the dependency tree and can't have forward references to module kind #2
2. Service/Component code: this code provides the implementation of some service or component. These are made up of two parts:
2.1 service-common directory: client code, these are types which must be shared and available to interact with, configure, reference the service; e.g., message types, component ids, service registration handling. these should never include service implementation code, nor should there be a build order between these directories (i.e., there shouldn't be dependencies between the 2.2 service directory: this code does whatever the service does
- Contact Info
- email: architecture@eucalyptus.com
- IRC: #eucalyptus-devel (freenode)
- Eucalyptus Links