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

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: