... | ... | @@ -8,7 +8,7 @@ The combination of these controls gives lots of flexibility e.g. applications ca |
|
|
|
|
|
# State diagram of an app
|
|
|
|
|
|
Every control is made by contacting the CAMEO server which is responsible to control the applications. Every Cameo application has a sequence of states. The following diagram shows the complete possibilities:
|
|
|
Every control is made by contacting the CAMEO server which is responsible to control the applications. Every CAMEO application has a sequence of states. The following diagram shows the complete possibilities:
|
|
|
|
|
|
![Application States](images/Application-states.png)
|
|
|
|
... | ... | @@ -213,7 +213,7 @@ This time we typed *ctl+c* to kill the app. We could have used *shift+s* to clea |
|
|
|
|
|
Some additional commands and features can be interesting to know.
|
|
|
|
|
|
We saw that by default *cmo* contacts the local CAMEO server on port 7000. You can change that by defining the *CAMEO_SERVER* environment variable e.g. with *tcp://localhost:8000* which can be useful if you configured the Cameo server with that port.
|
|
|
We saw that by default *cmo* contacts the local CAMEO server on port 7000. You can change that by defining the *CAMEO_SERVER* environment variable e.g. with *tcp://localhost:8000* which can be useful if you configured the CAMEO server with that port.
|
|
|
|
|
|
You can display the CAMEO server endpoint:
|
|
|
```
|
... | ... | |