... | ... | @@ -14,8 +14,13 @@ Following diagram shows a typical use case: |
|
|
|
|
|
![Typical use case](images/Typical-use-case.png)
|
|
|
|
|
|
Three computers are used: A, B, C. The applications App1 and App2 are installed on B and C.
|
|
|
A Cameo server is installed on the computers B and C.
|
|
|
Three computers are used: A, B, C. A Cameo server is installed on the computers B and C. The applications App1 and App2 are installed on B and C and registered into the Cameo servers.
|
|
|
Sequence of actions:
|
|
|
- The user uses the console to start the execution of App1 by contacting the Cameo server on B.
|
|
|
- The application App1 is starting and starts the execution of App2 by contacting the Cameo server on C.
|
|
|
- Once App2 has started, App1 is sending requests to App2 that is responding to App1.
|
|
|
- The user uses the console to stop the execution of App1.
|
|
|
- The application is stopping and stops App2.
|
|
|
|
|
|
# Cameo
|
|
|
The first goal of Cameo is to provide services for starting, stopping, synchronizing distributed applications. Cameo is an application-oriented middleware. The lifecycle of remote applications can be entirely managed either by the Cameo console or in an application by using the client API in C++, Java or Python.
|
... | ... | |