Difference between revisions of "EdgeServerCore"
From RifidiWiki
(→Overview) |
(→Overview) |
||
| Line 4: | Line 4: | ||
:The Configuration Framework handles persisting certain services, exposing them via JMX, and making them available in the OSGi registry | :The Configuration Framework handles persisting certain services, exposing them via JMX, and making them available in the OSGi registry | ||
;[[Reader Framework]] | ;[[Reader Framework]] | ||
| − | : | + | : The Reader Framework uses the [[Configuration Framework]] to expose readers as services to the rest of the edge server |
;[[Command Framework]] | ;[[Command Framework]] | ||
| − | : | + | :The Command Framework uses the [[Configuration Framework]] to expose commands as services to the rest of the edge server |
;[[RMI Interface]] | ;[[RMI Interface]] | ||
:The interface for programmatically interacting with the Edge Server | :The interface for programmatically interacting with the Edge Server | ||
Revision as of 16:45, 18 May 2009
Contents
Overview
< A paragraph about what the core does and basic structure >
- Configuration Framework
- The Configuration Framework handles persisting certain services, exposing them via JMX, and making them available in the OSGi registry
- Reader Framework
- The Reader Framework uses the Configuration Framework to expose readers as services to the rest of the edge server
- Command Framework
- The Command Framework uses the Configuration Framework to expose commands as services to the rest of the edge server
- RMI Interface
- The interface for programmatically interacting with the Edge Server
Architecture Overview
<Explain some basic terms & relationships: how readers, sessions, and commands interact>
OSGi
Services
<Services that are available for use, for example, DAOs>
Bundle Dependencies
< Graph displaying which bundles depend on each other > <TODO: Jochen>
ALE & ESPER
<TODO: Jochen>
