The PushSession class encapsulates the user-independent part of the processing involved in a push within an Agentry-based application.
All members of PushSession, including inherited members.
Constructors| Modifier and Type | Constructor | Description |
|---|---|---|
| public | PushSession(String, Server, SessionData) | Construct a new session. |
| Modifier and Type | Method | Description |
|---|---|---|
| public final void | beginPushError() | Deprecated. As of Agentry 5.2.8, code for this method should be moved into a subclass of PushUserSession. This method is no longer supported; it is here as a final declaration in order to force subclasses to be converted over to using PushUserSession. |
| public void | beginPushReadStep() | This method is called by the server prior to the execution of the "Object Read" steps for the push. |
| public void | beginPushRemoval() | This method is called by the server prior to the execution of the "Removal" steps for the push. |
| public final void | beginPushResponse() | Deprecated. As of Agentry 5.2.8, code for this method should be moved into a subclass of PushUserSession. This method is no longer supported; it is here as a final declaration in order to force subclasses to be converted over to using PushUserSession. |
| public void | beginPushRetrieval() | This method is called by the server prior to the execution of the "Retrieval" steps for the push. |
| public final void | endPushError() | Deprecated. As of Agentry 5.2.8, code for this method should be moved into a subclass of PushUserSession. This method is no longer supported; it is here as a final declaration in order to force subclasses to be converted over to using PushUserSession. |
| public void | endPushReadStep() | This method is called by the server after the "Object Read" Steps for the push have been successfully executed. |
| public void | endPushRemoval() | This method is called by the server after the "Removal" steps for the push have been successfully executed. |
| public final void | endPushResponse() | Deprecated. As of Agentry 5.2.8, code for this method should be moved into a subclass of PushUserSession. This method is no longer supported; it is here as a final declaration in order to force subclasses to be converted over to using PushUserSession. |
| public void | endPushRetrieval() | This method is called by the server after the "Retrieval" steps for the push have been successfully executed. |
| Modifier and Type | Member | Description |
|---|---|---|
| public final void | debug(String) | Write the given message to a debug log, if debugging is enabled. |
| public String | getName() | Returns the name of the session, as configured in the Agentry application. |
| public Server | getServer() | Returns the Server singleton object that the Java system connection is currently using. |
| public SessionData | getSessionData() | Returns the session data for this session. |
| public User | getUser() | Returns the user for this session, if any. |
| protected | Session(String, Server, SessionData, User) | Construct a new session, and save each of the arguments so that they can be retrieved later via the getName(), getServer(), getSessionData(), and getUser() methods. |
| protected | Session(String, Server, SessionData) | Construct a new session, and save each of the arguments so that they can be retrieved later via the getName(), getServer(), and getSessionData() methods. |
| public void | sessionAborted() | This is called if the session is aborted (e.g., by an exception). |
In brief, a push is an application component that defines the transfer of data between the client and the server. Unlike fetches, the transfer within a push is initiated by the server, rather than the client. A push is made up of steps, grouped in varying categories. The steps in each of these groups are run separately. The groups are "Retrieval", "Removal", "Object Read", "Response" and "Error"; this class handles the "Retrieval", "Removal", and "Object Read" step groups, as those are independent of users. The remaining groups, "Response" and "Error", are user-dependent and are handled by the PushUserSession class.
This class contains methods to perform actions before and after each of these groups of steps. The default implementation of these methods in the AJAPI perform no additional specific actions. A designer can extend this class if special processing is required before or after each of these groups of steps are processed. If this class is extended, the Server class must also be extended and its createPushSession method must be overridden to return the new subclass.