ICEpush
  1. ICEpush
  2. PUSH-252

Simplify ICEpush client configuration

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.3
          • Fix Version/s: 4.0.BETA, 4.0
          • Component/s: JavaScript Client
          • Labels:
            None
          • Environment:
            ICEpush, JavaScript
          • Assignee Priority:
            P1

            Description

            ICEpush is cumbersome to set up from JavaScript:


            <script type="text/javascript" src="http://labs.icesoft.com/push/code.icepush"></script>
            <script type="text/javascript">
                ice.push.configuration.contextPath =
                        "http://labs.icesoft.com/push/";
                ice.push.configuration.blockingConnectionURI =
                        "http://labs.icesoft.com/push/listen.icepush";
                ice.push.configuration.createPushIdURI =
                        "http://labs.icesoft.com/push/create-push-id.icepush";
                ice.push.configuration.notifyURI =
                        "http://labs.icesoft.com/push/notify.icepush";
                ice.push.configuration.addGroupMemberURI =
                        "http://labs.icesoft.com/push/add-group-member.icepush";
                ice.push.configuration.removeGroupMemberURI =
                        "http://labs.icesoft.com/push/remove-group-member.icepush";


            This should either be automatic from the URL the script is loaded from (if possible) or should work with just ice.push.configuration.contextPath set and the others determined automatically.

              Activity

              Hide
              Permalink
              Mircea Toma added a comment -

              Changed bridge configuration to infer request URLs based on partial or without configuration defined.

              The context path is set to '.' by default. It can be set to null in which case the context path will be calculated from the browser's URL. Also the path can be defined as absolute or relative. For the other parameters the default values are used when not provided, which are: listen.icepush, create-push-id.icepush, notify.icepush, add-group-member.icepush, remove-group-member.icepush.
              The URI parameters can be defined as absolute or relative. When they are relative the defined or inferred context path is used to resolve the final URL.

              Show
              Mircea Toma added a comment - Changed bridge configuration to infer request URLs based on partial or without configuration defined. The context path is set to '.' by default. It can be set to null in which case the context path will be calculated from the browser's URL. Also the path can be defined as absolute or relative. For the other parameters the default values are used when not provided, which are: listen.icepush, create-push-id.icepush, notify.icepush, add-group-member.icepush, remove-group-member.icepush. The URI parameters can be defined as absolute or relative. When they are relative the defined or inferred context path is used to resolve the final URL.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: