Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Fix Version/s: 2.0.0
-
Component/s: Java Client, Push Library
-
Labels:None
-
Environment:ICEpush
Description
Introduce an alternative way to receive the BROWSER_ID. Currently the first request to an ICEpush application, in the case of a JSP application it would be to index.jsp, the BROWSER_ID is returned in the response's Set-Cookie header. A BROWSER_ID is required in order to successfully utilize the Push API, such as create-push-id, add-group-member and such. However, in the case of the Java Push Client, there is no page required to display. Therefore a first request to index.jsp should not have to be issued by the Java Push Client. Its first request should rather be the create-push-id request for instance. However, at this point the Java Push Client does not have a BROWSER_ID yet.
Issue Links
- blocks
-
PUSH-83
ICEpush Java Client
-
- Open
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Changed ConfigurationServer to generate and send a browserId on the blocking conection in case the browser dind't get on yet (during page load for example).
The browserID is sent as a command to the ICEpush bridge, once received the bridge will set the corresponding cookie. This mechanism is necessary because using Set-Cookie header on an AJAX response method is ignored by the browser.
Show
Mircea Toma
added a comment - Changed ConfigurationServer to generate and send a browserId on the blocking conection in case the browser dind't get on yet (during page load for example).
The browserID is sent as a command to the ICEpush bridge, once received the bridge will set the corresponding cookie. This mechanism is necessary because using Set-Cookie header on an AJAX response method is ignored by the browser.
Assigning to Mircea for investigation.