THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Master Slave SOAP/REST API
Slave has configuration values:
- cluster.isSlave ("true", or 1 to enable slave)
- cluster.master.host (IP/host of master)
- cluster.master.http.port (Http port of master)
- cluster.master.soap.user (SOAP User for accessing the API on master)
- cluster.master.soap.pass (SOAP Pass for accessing the API on master)
In the Spring configuration you can also configure the time in milliseconds for the ping to the master.
SOAP REST API calls:
Name | Description | Link |
|---|---|---|
ping | master is noitified by slave, includes slave userload | |
addFlvRecording | master is notified by slave about new recording, includes recording meta data |
Master to slave communication:
After master receives addFlvRecording via SOAP, Master does load via HTTP the recordings to the master file-system.
As long as the sync to the master database is in progress, the recording UI has to show a message if the user clicks on the recording in the UI.