ICEpush
  1. ICEpush
  2. PUSH-114

Separate configuration of API URIs and blocking connection URI

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Beta
          • Fix Version/s: 2.0.1
          • Component/s: Push Library
          • Labels:
            None
          • Environment:
            supported browsers

            Description

            When deploying ICEpush with EPS the requests initiated by the JS API need to be sent to the server/context that instantiated the ICEpush bridge instead of going to the EPS server/context.

              Activity

              Hide
              Permalink
              Mircea Toma added a comment -

              Changed configuration of ICEpush to allow for separate configuration of the blocking connection URI from the API URIs.
              When org.icepush.contextPath context parameter is defined the bridge is configured with a URI of the form /

              {contextPath}

              /listen.icepush while the rest of the URIs are still using the pattern defined in ice.push.configuration.uriPattern JS property.

              Show
              Mircea Toma added a comment - Changed configuration of ICEpush to allow for separate configuration of the blocking connection URI from the API URIs. When org.icepush.contextPath context parameter is defined the bridge is configured with a URI of the form / {contextPath} /listen.icepush while the rest of the URIs are still using the pattern defined in ice.push.configuration.uriPattern JS property.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: