Difference between revisions of "The server side of CCIL"
From CCIL
| Line 14: | Line 14: | ||
* Communication between components. | * Communication between components. | ||
** Within the same server. | ** Within the same server. | ||
| − | ** On a remote machine. | + | ** On a [http://cybercore.sourceforge.net/documentation/index.php/Connectors remote machine]. |
== CyberCore == | == CyberCore == | ||
By its nature, ''CCIL'' is a ''CyberCore'' server. It is the second extension of the framework and brings in the analytical edge. There is third extension, this time on ''CCIL'' itself - it is called ''Trinity'' and was developed for the [http://identrics.net/ Identrics] company. | By its nature, ''CCIL'' is a ''CyberCore'' server. It is the second extension of the framework and brings in the analytical edge. There is third extension, this time on ''CCIL'' itself - it is called ''Trinity'' and was developed for the [http://identrics.net/ Identrics] company. | ||
Revision as of 08:17, 9 June 2017
CCIL can execute in two modes, each able to spawn the other. On can say it has two aspects:
- Analytical
- Serving
This article focuses on the second one. If you want to read about the analytical aspect, please visit: The analytical side of CCIL.
The server-side aspect of the framework is best covered by the documentation of its underlying layer - CyberCore.
In short, this is the ability to register components (POJOs) and enable them to communicate between themselves and publishing their functionalities to the outside world:
- Component register - Binding a POJO with some pre-defined name.
- Ability to supply configuration parameters.
- Communication between components.
- Within the same server.
- On a remote machine.
CyberCore
By its nature, CCIL is a CyberCore server. It is the second extension of the framework and brings in the analytical edge. There is third extension, this time on CCIL itself - it is called Trinity and was developed for the Identrics company.
