added a comment - - edited
(5) i'm concerned that a jquery plugin was added in this issue, but it was never mentioned in svn commit messages. shouldn't we document (somewhere) what other software is includes ?
Eduards Samersovs RESOLVED, see http://zabbix.org/wiki/Docs/specs/ZBXNEXT-1398#Specification
<richlv> looking good for this issue, but it mentions two new configuration parameters. where are they exposed to user ? defines.inc.php ?
Eduards Samersovs Yes, all our parameters are stored in one file..
<richlv> then they should be documented in http://www.zabbix.com/documentation/2.0/manual/web_interface/definitions
that should mention from which version they are available, and also should be done for 2.2 docs
Eduards Samersovs RESOLVED
<richlv> doesn't mention the version from which they will be available (2.0.4, i assume)
as for params, SCREEN_REFRESH_TIMEOUT is just that - if we haven't been able to update an element for n seconds, it will be darkened, right ?
SCREEN_REFRESH_RESPONSIVENESS is a bit unclear still - what's the purpose of it ?
Eduards Samersovs SCREEN_REFRESH_TIMEOUT yes you understand right. SCREEN_REFRESH_RESPONSIVENESS is useful for example in second use case:
Update interval is 5 minutes. SCREEN_REFRESH_RESPONSIVENESS is 10 seconds. Server/browser built-in timeout (for example) is 10 minutes. User click on screen for update. Request is sending. Server is crashed at this time and don't send response. Browser just wait.. Any user clicking after what will be ignored until response will be received. So we will wait until next update planing time (5 minutes) will happens. But! SCREEN_REFRESH_RESPONSIVENESS defines time after witch user click will generate new request and define new time point after witch next clicking will be ignored. So, maybe at this time server will be live and response will be received. If server finally reacts on first request and send response - it will be validated on timestamps and will be ignored if second request get a latest data. So, without SCREEN_REFRESH_RESPONSIVENESS user can wait 5 minutes to get a data, but with this param user will wait only 10 seconds + request/response time.
<richlv> ok, one last thing...
what does "User click on screen for update" include ? changing time period ? anything else ?
Eduards Samersovs May say any user action witch lead to data update..
<richlv> but i have a hard time imagining other user action than changing the time period - what else could there be ? (in screens)
Eduards Samersovs Rich, do you want a list with possible user action witch leads to screen updates? Read documentation or ask documentors. For this task main goal is process update action and that has served for this action is not important! Sorry I don't understand you idea..