dbp::daemon_application_int Class Reference
Daemon application interface. More...
#include <daemon_application.h>
Public Types | |
| typedef delegate0< void > | on_reload_configuration_handler |
| Reload application configuration signal handler. | |
| typedef delegate0< void > | on_pause_handler |
| Pause signal handler. | |
| typedef delegate0< void > | on_resume_handler |
| Resume signal handler. | |
| typedef delegate0< void > | on_terminate_handler |
| Terminate signal handler. | |
Public Member Functions | |
| virtual void | log (const std::string &message, log_level::log_level level=log_level::info)=0 |
| Write to the system log. | |
| virtual void | on_reload_configuration (on_reload_configuration_handler handler)=0 |
| Register "reload application configuration" signal handler. | |
| virtual void | on_pause (on_pause_handler handler)=0 |
| Register "pause" signal handler. | |
| virtual void | on_resume (on_resume_handler handler)=0 |
| Register "resume" signal handler. | |
| virtual void | on_terminate (on_terminate_handler handler)=0 |
| Register "terminate" signal handler. | |
Detailed Description
Daemon application interface.
Each concrete daemon application should implement this interface by implementing pure virtual methods.
Member Function Documentation
| virtual void dbp::daemon_application_int::log | ( | const std::string & | message, | |
| log_level::log_level | level = log_level::info | |||
| ) | [pure virtual] |
Write to the system log.
Daemon applications should not to display any information to the console, so you should call this method to write any information into the system log.
- Parameters:
-
message the information to log. level the log level.
Implemented in dbp::daemon_application.
Referenced by dbp::daemon_application::log().
| virtual void dbp::daemon_application_int::on_pause | ( | on_pause_handler | handler | ) | [pure virtual] |
Register "pause" signal handler.
The "pause" signal is raised when an user wants to pause the application. If your application should react to pause (by stopping calculations or dropping new connections), you should register your own signal handler.
- Parameters:
-
handler the signal handler delegate
Implemented in dbp::daemon_application.
Referenced by dbp::daemon_application::on_pause().
| virtual void dbp::daemon_application_int::on_reload_configuration | ( | on_reload_configuration_handler | handler | ) | [pure virtual] |
Register "reload application configuration" signal handler.
If your application implements of on-the-fly reconfiguration, you should register your own signal handler. This signal is raised when an user wants to reload daemon configuration file to apply new configuration parameters.
- Parameters:
-
handler the signal handler delegate
Implemented in dbp::daemon_application.
Referenced by dbp::daemon_application::on_reload_configuration().
| virtual void dbp::daemon_application_int::on_resume | ( | on_resume_handler | handler | ) | [pure virtual] |
Register "resume" signal handler.
The "resume" signal is raised when an user wants to continue the running of application. If your application should react to resume (by starting calculations or accepting new connections), you should register your own signal handler.
- Parameters:
-
handler the signal handler delegate
Implemented in dbp::daemon_application.
Referenced by dbp::daemon_application::on_resume().
| virtual void dbp::daemon_application_int::on_terminate | ( | on_terminate_handler | handler | ) | [pure virtual] |
Register "terminate" signal handler.
The "terminate" signal is raised when an user wants to stop the application. If your application should react to terminating (flushing buffers, etc.), you should register your own signal handler.
- Parameters:
-
handler the signal handler delegate
Implemented in dbp::daemon_application.
Referenced by dbp::daemon_application::on_terminate().
The documentation for this class was generated from the following file:
