mirror of https://github.com/Icinga/icinga2.git
ed2ebdf0d0
Use case: a reader subscribes to config changes. As they happen rarely, chances are good that the connection will time out in the meantime. Now, a reconnect is easy - but you wouldn't know whether you missed any config changes. So you are required to issue a new sync to be on the safe side. Given a 60sec connection timeout (think: SSL layer, firewalls etc) when no traffic happens this would be too expensive. Some kind of a heartbeat available for subscription would allow subscribers to artificially keep the connection alive. As a first simple solution to this I'd suggest to publish CIB data, that might be useful anyways. refs #4991 fixes #5098 Signed-off-by: Michael Friedrich <michael.friedrich@icinga.com> |
||
|---|---|---|
| .. | ||
| base | ||
| checker | ||
| cli | ||
| compat | ||
| config | ||
| db_ido | ||
| db_ido_mysql | ||
| db_ido_pgsql | ||
| demo | ||
| hello | ||
| icinga | ||
| livestatus | ||
| methods | ||
| notification | ||
| perfdata | ||
| redis | ||
| remote | ||
| CMakeLists.txt | ||