Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Aperi/architecture"
(→Overview Component Designs) |
m (adding a link to the wef design) |
||
| Line 28: | Line 28: | ||
* [[Aperi Database R2 Extensibility]] | * [[Aperi Database R2 Extensibility]] | ||
* [[Aperi Agent R2 Extensibility]] | * [[Aperi Agent R2 Extensibility]] | ||
| + | |||
| + | == R3 Designs === | ||
| + | * [http://www.eclipse.org/aperi/tech/WEF_Design.doc WEF Events Design (MS Word)] | ||
Revision as of 14:23, 6 February 2007
Contents
This page is a collection of information regarding the architecture of Aperi.
Overview Component Designs
- Database Component Design (MS Word)
- Device Server Component Design (MS Word)
- Disk Manager Component Design (MS Word)
- Fabric Manager Component Design (MS Word)
- JLog (Logging API) User's Guide
R2 Designs
- Aperi Agent Design R2
- Aperi Connector Design R2
- Aperi Data Server Design R2
- Aperi Device Server Design R2
- Material from Tech Face to Face in July 2006
- Aperi Performance Issues using Derby as Repository
R2 API Documentation
- Aperi Data Server R2 Extensibility
- Aperi Device Server R2 Extensibility
- Aperi Database R2 Extensibility
- Aperi Agent R2 Extensibility