Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8RC2, 1.8
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Req. whenever multiple ICEfaces asynchronous apps (push) are deployed to the same server/host. Also required for support of multiple ICEfaces push portlets on the same portlet page.
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration

      Description

      The ICEfaces Push Server is a replacement for the Async. HTTP Server (AHS). It provides a zero-configuration solution to the problem of supporting multiple ICEfaces asynchonrous (push) applications deployed to the same server/host-name. As most browsers have limitations on the number of concurrent connections that can be made to the same server/host-name it is necessary for multiple async. apps. on the same server to share a blocking connection back to the server. The Push Server provides this functionality in a lightweight implementation with minimal configuration required.

      To use the Push Server, you simply deploy the push-server.war file to the same server you are deploying your ICEfaces push applications to. The ICEfaces apps. will discover the Push Server at startup and automatically configure themselves to use it.

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Jack Van Ooststroom
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: