ICEpush
  1. ICEpush
  2. PUSH-28

Introduction of ICEpush EPS

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: EE 3.0.0
          • Component/s: Push Server
          • Labels:
            None
          • Environment:
            ICEpush, ICEpush EPS

            Description

            Introduce "ICEpush EPS"

              Issue Links

              blocks

              Task - A task that needs to be done. PUSH-2 ICEpush multi framework sample

              • Major - Major loss of function.
              • Closed
              depends on

              New Feature - A new feature of the product, which has yet to be developed. PUSH-122 Create Servlet 2.5 and 3.0 build tasks for EPS

              • Major - Major loss of function.
              • Open

              New Feature - A new feature of the product, which has yet to be developed. PUSH-33 Add the ability to set the blocking connection context on the JavaScript Bridge

              • Major - Major loss of function.
              • Closed

              Task - A task that needs to be done. PUSH-119 Change the project structure of ICEpush EE

              • Major - Major loss of function.
              • Closed

                Activity

                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Certification of stand-alone and cluster environments of the Enterprise Push Server has been addressed in: http://jira.icefaces.org/browse/IPCK-258

                Documentation describing EPS can be found at http://wiki.icesoft.com/display/IFEE2/Enterprise+Push+Server and related Wiki pages.

                To summarize:

                • EPS does not rely on and therefore does not utilize HTTP Sessions
                • EPS fully supports load-balancing, session stickiness and non-stickiness, and fail-over
                • EPS supports stand-alone environments on GlassFish Server 3, JBoss AS 6, Tomcat 6/7, WebLogic Server 10.3 and WebSphere Application Server 7
                • EPS supports cluster environments on Tomcat 6/7 and WebSphere Application Server 7
                • EPS inherits Servlet 3.0 ARP support from ICEpush

                Marking this one as FIXED.

                Show
                Jack Van Ooststroom added a comment - Certification of stand-alone and cluster environments of the Enterprise Push Server has been addressed in: http://jira.icefaces.org/browse/IPCK-258 Documentation describing EPS can be found at http://wiki.icesoft.com/display/IFEE2/Enterprise+Push+Server and related Wiki pages. To summarize: EPS does not rely on and therefore does not utilize HTTP Sessions EPS fully supports load-balancing, session stickiness and non-stickiness, and fail-over EPS supports stand-alone environments on GlassFish Server 3, JBoss AS 6, Tomcat 6/7, WebLogic Server 10.3 and WebSphere Application Server 7 EPS supports cluster environments on Tomcat 6/7 and WebSphere Application Server 7 EPS inherits Servlet 3.0 ARP support from ICEpush Marking this one as FIXED.

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: