... | ... | @@ -29,4 +29,16 @@ Once the Cameo server is changing the state of an application, it also publishes |
|
|
|
|
|
# Events in the API and the console
|
|
|
|
|
|
Let's take a concrete example and show how to do it with the API and the console. Here is the diagram showing the interactions:
|
|
|
|
|
|
![Control the apps](images/Control-the-apps.png)
|
|
|
|
|
|
Sequence of actions:
|
|
|
* The application *App1* on *A* is contacting the Cameo server on *B* to start *App2*.
|
|
|
* The application *App2* is running on *B*.
|
|
|
* The application *App3* on *C* is contacting the Cameo server on *B* to connect *App2*.
|
|
|
* The console on *D* is contacting the Cameo server on *B* to connect *App2*.
|
|
|
* The application *App3* on *C* stops *App2*.
|
|
|
* The applications *App1* and console are notified that *App2* stopped.
|
|
|
|
|
|
|