Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2, EE-3.2.0.GA
-
Fix Version/s: 3.3, EE-3.3.0.GA
-
Component/s: JavaScript Client, Push Library
-
Labels:None
-
Environment:Cluster environment
Description
In order to correctly support the adaptive heartbeat in cluster environments the timestamp for the heartbeat update must be moved to the HTTP response. The JavaScript bridge in its turn needs to echo this back to the server. This is needed as multiple nodes may handle a single browser instance. In order to correctly calculate the adaptive heartbeat and the determination of when to do this, relies on the value of the timestamp of the heartbeat update. By making this part of the response/request cycle every node in the cluster can know the timestamp of the heartbeat update.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I introduced a new HTTP response extension header named ice.push.heartbeatTimestamp. This header is echoed back by the JavaScript bridge if it is present. The value of this header is the leading value used by the AdjustableHeartbeatServer. Marking this as FIXED.
Show
Jack Van Ooststroom
added a comment - I introduced a new HTTP response extension header named ice.push.heartbeatTimestamp. This header is echoed back by the JavaScript bridge if it is present. The value of this header is the leading value used by the AdjustableHeartbeatServer. Marking this as FIXED.
Sending icepush-ee/core/src/main/javascript/application.js
Transmitting file data .
Committed revision 33550.
Sending icepush-ee/core-ee/src/main/java/com/icesoft/icepush/AdjustHeartbeatServer.java
Transmitting file data .
Committed revision 33725.