Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Documentation/ConnectivityManager"
(→API) |
(→API) |
||
Line 5: | Line 5: | ||
== API == | == API == | ||
− | See javadoc: [http://build.eclipse.org/rt/smila/javadoc/current/org/eclipse/smila/connectivity/ConnectivityManager.html] | + | See javadoc: [http://build.eclipse.org/rt/smila/javadoc/current/org/eclipse/smila/connectivity/ConnectivityManager.html org.eclipse.smila.connectivity.ConnectivityManager] |
== Implementations == | == Implementations == |
Revision as of 02:58, 21 April 2011
Contents
Overview
The Connectivity Manager is the single point of entry for data in the SMILA. It's functionality is divided into several Sub-Components for better modularization. The Connectivity Manager and its Sub-Components are implemented as Java OSGi services.
API
See javadoc: org.eclipse.smila.connectivity.ConnectivityManager
Implementations
It is possible to provide different implementations for the ConnectivityManager interface. At the moment there is one implementation available.
org.eclipse.smila.connectivity.impl
This bundle contains the default implementation of the ConnectivityManager interface.
The ConnectivityManagerImpl contains the core execution logic as it does the actual processing of the incoming requests. Incoming Record objects are split into different parts:
- metadata (record attributes) is stored via the Blackboard Service in the RecordStorage
- attachments are stored via the Blackboard Service in the BinaryStorage
- a message object is added to a Queue containing the record Id and optional any additional metadata
This chart shows the Connectivity Manager implementation, it's Sub-Components and the relationship to other components:
Sub-Components
Router
The Router routes messages to the Queue(s) according to it's configuration. See SMILA/Documentation/QueueWorker for more information.
Buffer
Not yet implemented.
Configuration
There are no configuration options available for this bundle.