The org.zkoss.zk.ui.util.Monitor interface"
From Documentation
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{ZKConfigurationReferencePageHeader}} | {{ZKConfigurationReferencePageHeader}} | ||
| − | |||
| − | |||
| − | + | '''Listener:''' | |
| + | org.zkoss.zk.ui.util.Monitor | ||
| − | + | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.Monitor</javadoc> to monitor the statuses of ZK. Unlike other listeners, there is at most one monitor listener for each Web application. If you like, you can chain them together manually. | |
| − | + | ZK provides an implementation named <javadoc>org.zkoss.zk.ui.util.Statistic</javadoc>, which accumulates the statistic data in the memory. It is a good starting point to understand the loading of your ZK application. | |
| + | |||
| + | '''Instantiation:''' | ||
| + | Unlike most other listeners, at most one monitor instance is created in one application. | ||
| + | In addition, it is shared, so the implementation must be thread-safe. | ||
| + | |||
| + | {{ZKConfigurationReferencePageFooter}} | ||
Latest revision as of 08:01, 20 December 2023
Listener:
org.zkoss.zk.ui.util.Monitor
A listener could implement Monitor to monitor the statuses of ZK. Unlike other listeners, there is at most one monitor listener for each Web application. If you like, you can chain them together manually.
ZK provides an implementation named Statistic, which accumulates the statistic data in the memory. It is a good starting point to understand the loading of your ZK application.
Instantiation: Unlike most other listeners, at most one monitor instance is created in one application. In addition, it is shared, so the implementation must be thread-safe.