I think it would be useful to have an explicit top-level timestamp
information for each nodes stats response. By timestamp I mean information
about time a particular response is relevant to. I know there are several
timestamps nested inside the response but they are relevant to respective
sub/parts of the response and not every sup/part has its own timestamp
(roughly half of them do not have it). This can make it hard if you want to
sort values correctly because you should not rely either on AJAX response
arrival time or AJAX request time. What we really need is the time when
this request was processed on the server side. Or am I missing something
here?
This is probably not a big problem in general but it can hit you when you
really try to use and display response data precisely (like in bigdesk).
I think it would be useful to have an explicit top-level timestamp
information for each nodes stats response. By timestamp I mean information
about time a particular response is relevant to. I know there are several
timestamps nested inside the response but they are relevant to respective
sub/parts of the response and not every sup/part has its own timestamp
(roughly half of them do not have it). This can make it hard if you want to
sort values correctly because you should not rely either on AJAX response
arrival time or AJAX request time. What we really need is the time when
this request was processed on the server side. Or am I missing something
here?
This is probably not a big problem in general but it can hit you when you
really try to use and display response data precisely (like in bigdesk).
I think it would be useful to have an explicit top-level timestamp
information for each nodes stats response. By timestamp I mean information
about time a particular response is relevant to. I know there are several
timestamps nested inside the response but they are relevant to respective
sub/parts of the response and not every sup/part has its own timestamp
(roughly half of them do not have it). This can make it hard if you want to
sort values correctly because you should not rely either on AJAX response
arrival time or AJAX request time. What we really need is the time when
this request was processed on the server side. Or am I missing something
here?
This is probably not a big problem in general but it can hit you when you
really try to use and display response data precisely (like in bigdesk).
I think it would be useful to have an explicit top-level timestamp
information for each nodes stats response. By timestamp I mean information
about time a particular response is relevant to. I know there are several
timestamps nested inside the response but they are relevant to respective
sub/parts of the response and not every sup/part has its own timestamp
(roughly half of them do not have it). This can make it hard if you want to
sort values correctly because you should not rely either on AJAX response
arrival time or AJAX request time. What we really need is the time when
this request was processed on the server side. Or am I missing something
here?
This is probably not a big problem in general but it can hit you when
you really try to use and display response data precisely (like in bigdesk).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.