Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Fix Version/s: 2.0-Beta
-
Component/s: Push Library, Push Server
-
Labels:None
-
Environment:ICEpush
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
We should reconsider the uriPrefix and uriSuffix strategy which currently relates to the configuration.icepush request. With this implementation there seems to be a nasty cashing issue. We should consider switching to HTTP permanent redirect for instance and step away from the requirement of having the developer change the application by adding the script tag in order to get the configuration.icepush.
The following configuration parameters were introduced:
org.icepush.heartbeatTimeout (default value = 50000ms)
When blocking connection is blocked for more time (defined in milliseconds) than this parameters specifies the bridge assumes that the connection is in trouble (and will retry to reconnect twice before giving up).
org.icepush.serverErrorRetryTimeouts (default values = 1000ms 2000ms 4000ms)
A list of space separated intervals (defined in milliseconds) used by the bridge to retry connecting to the server after a server side error is received.
org.icepush.fileExtension (default value = "")
This parameter will append the defined file extension to the request URIs used by the bridge to communicate with the server.
org.icepush.contextPath (no default value)
This parameter will force the bridge to use the defined context path when initiating the blocking request.