ICEpush
  1. ICEpush
  2. PUSH-101

Introduce alternative way to receive BROWSER_ID

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major 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

              New Feature - A new feature of the product, which has yet to be developed. PUSH-83 ICEpush Java Client

              • Major - Major loss of function.
              • Open

                Activity

                Ascending order - Click to sort in descending order
                Jack Van Ooststroom created issue -
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Assigning to Mircea for investigation.

                Show
                Jack Van Ooststroom added a comment - Assigning to Mircea for investigation.
                Jack Van Ooststroom made changes -
                Field Original Value New Value
                Assignee Mircea Toma [ mircea.toma ]
                Jack Van Ooststroom made changes -
                Link This issue blocks PUSH-83 [ PUSH-83 ]
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #22320 Mon Sep 13 06:25:56 MDT 2010 mircea.toma PUSH-101 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).
                Files Changed
                Commit graph ADD /scratchpads/snowplow/core/src/main/java/org/icepush/http/standard/Cookie.java
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/PushContext.java
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/servlet/BrowserBoundServlet.java
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/ConfigurationServer.java
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/javascript/command.js
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/javascript/application.js
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #22321 Mon Sep 13 06:30:18 MDT 2010 mircea.toma PUSH-101 Revert commented out code.
                Files Changed
                Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/PushContext.java
                Hide
                Permalink
                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.

                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.
                Mircea Toma made changes -
                Status Open [ 1 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]
                Ken Fyten made changes -
                Fix Version/s 2.0.0 [ 10233 ]
                Ken Fyten made changes -
                Status Resolved [ 5 ] Closed [ 6 ]

                  People

                  • Assignee:
                    Mircea Toma
                    Reporter:
                    Jack Van Ooststroom
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: