Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
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.
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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The new Push Server has been added at /icefaces/push-server. The documentation has been updated with a specific Push Server section. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - The new Push Server has been added at /icefaces/push-server. The documentation has been updated with a specific Push Server section. Marking this one as FIXED.
Can't always use Servlet 2.4 API: getLocalAddr() and getLocalPort()
Show
Jack Van Ooststroom
added a comment - Can't always use Servlet 2.4 API: getLocalAddr() and getLocalPort()
Servlet 2.4 methods are now only used when Servlet 2.4 or higher is detected. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - Servlet 2.4 methods are now only used when Servlet 2.4 or higher is detected. Marking this one as FIXED.
- If the target Application Server supports Servlet 2.4, adding Push Server in the mix is completely configureless.
- If the target Application Server does not support Servlet 2.4 or if a Portal Server is used AND the Application or Portal Server runs using a port different from the default port, custom configuration of the web.xml is required.
The IP address and port # used by the Application server can be configured as required using the following config. parameters (in the web.xml file):
- "com.icesoft.faces.localAddress"
- "com.icesoft.faces.localPort"
Show
Ken Fyten
added a comment -
If the target Application Server supports Servlet 2.4, adding Push Server in the mix is completely configureless.
If the target Application Server does not support Servlet 2.4 or if a Portal Server is used AND the Application or Portal Server runs using a port different from the default port, custom configuration of the web.xml is required.
The IP address and port # used by the Application server can be configured as required using the following config. parameters (in the web.xml file):
"com.icesoft.faces.localAddress"
"com.icesoft.faces.localPort"
Changed Fix Version(s) to 1.8.0-RC2