The org.zkoss.zk.ui.util.Monitor interface"
From Documentation
m |
|||
| Line 4: | Line 4: | ||
org.zkoss.zk.ui.util.Monitor | 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 | + | 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 load of your ZK application. | 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 load of your ZK application. | ||
Revision as of 02:11, 8 August 2011
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 load of your ZK application.
Instantiation: Unlike most other listeners, at most one monitor is allowed in one application. In additions, it is shared, so the implementation must be thread safe.