Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.7.1
-
Component/s: None
-
Labels:None
-
Environment:ICEfaces, Ajax Push
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
The current RenderManager API offers a high degree of control over server-initiated rendering, but provides more power than necessary for simple applications. The SessionRenderer provides a more basic API as follows:
public class org.icefaces.application.SessionRenderer extends java.lang.Object{
public static synchronized void addCurrentSession(java.lang.String groupName);
public static synchronized void removeCurrentSession(java.lang.String groupName);
public static void render(java.lang.String groupName);
}
A sample invocation, such as in the auctionMonitor would be
In a bean constructor:
SessionRenderer.addCurrentSession("auction");
When an event occurs:
SessionRenderer.render("auction");
The SessionRenderer is responsible for the maintenance of the lists of HttpSessions/PortletSessions. Lists of Views are obtained from the ICEfaces infrastructure. RenderingException is not passed to the application because, in this case, the application is only concerned with pushing updates to active users. If users are not active, they are automatically garbage collected.
public class org.icefaces.application.SessionRenderer extends java.lang.Object{
public static synchronized void addCurrentSession(java.lang.String groupName);
public static synchronized void removeCurrentSession(java.lang.String groupName);
public static void render(java.lang.String groupName);
}
A sample invocation, such as in the auctionMonitor would be
In a bean constructor:
SessionRenderer.addCurrentSession("auction");
When an event occurs:
SessionRenderer.render("auction");
The SessionRenderer is responsible for the maintenance of the lists of HttpSessions/PortletSessions. Lists of Views are obtained from the ICEfaces infrastructure. RenderingException is not passed to the application because, in this case, the application is only concerned with pushing updates to active users. If users are not active, they are automatically garbage collected.
Issue Links
- depends on
-
ICE-2742 Broadcast rendering API
- Closed
Prototype implemented, pending checkin.