The max-process-time Element"
From Documentation
m (Created page with '{{ZKConfigurationReferencePageHeader}} =Version History= {{LastUpdated}} {| border='1px' | width="100%" ! Version !! Date !! Content |- | | | |} {{ZKConfig…') |
m |
||
Line 1: | Line 1: | ||
{{ZKConfigurationReferencePageHeader}} | {{ZKConfigurationReferencePageHeader}} | ||
+ | |||
+ | '''Syntax:''' | ||
+ | <max-process-time>''a_number''</max-process-time> | ||
+ | |||
+ | [Default: 3000] | ||
+ | |||
+ | It specifies the maximal allowed time to process events, in milliseconds. It must be positive. ZK will keep processing the requests until all requests are processed, or the maximal allowed time expires. | ||
+ | |||
+ | Notice that This setting has no effect on AU requests. Rather, it controls the number of the requests caused by the client-polling server push. In other words, if there are multiple pending server-push based on the client-polling, ZK will handle them one-by-one until all are served or the time expires. | ||
=Version History= | =Version History= |
Revision as of 15:30, 4 December 2010
Syntax:
<max-process-time>a_number</max-process-time>
[Default: 3000]
It specifies the maximal allowed time to process events, in milliseconds. It must be positive. ZK will keep processing the requests until all requests are processed, or the maximal allowed time expires.
Notice that This setting has no effect on AU requests. Rather, it controls the number of the requests caused by the client-polling server push. In other words, if there are multiple pending server-push based on the client-polling, ZK will handle them one-by-one until all are served or the time expires.
Version History
Version | Date | Content |
---|---|---|