Abstract: The present invention is an enhanced staged event-driven architecture (SEDA) stage. The enhanced SEDA stage can include an event queue configured to enqueue a plurality of events, an event handler programmed to process events in the event queue, and a thread pool coupled to the event handler. A resource manager further can be coupled to the thread pool and the event queue. Moreover, the resource manager can be programmed to allocate additional threads to the thread pool where a number of events enqueued in the event queue exceeds a threshold value and where all threads in the thread pool are busy.

Abstract: The present invention is an enhanced staged event-driven architecture (SEDA) stage. The enhanced SEDA stage can include an event queue configured to enqueue a plurality of events, an event handler programmed to process events in the event queue, and a thread pool coupled to the event handler. A resource manager further can be coupled to the thread pool and the event queue. Moreover, the resource manager can be programmed to allocate additional threads to the thread pool where a number of events enqueued in the event queue exceeds a threshold value and where all threads in the thread pool are busy.

Abstract: The present invention is an enhanced staged event-driven architecture (SEDA) stage. The enhanced SEDA stage can include an event queue configured to enqueue a plurality of events, an event handler programmed to process events in the event queue, and a thread pool coupled to the event handler. A resource manager further can be coupled to the thread pool and the event queue. Moreover, the resource manager can be programmed to allocate additional threads to the thread pool where a number of events enqueued in the event queue exceeds a threshold value and where all threads in the thread pool are busy.

Abstract: The present invention is an enhanced staged event-driven architecture (SEDA) stage. The enhanced SEDA stage can include an event queue configured to enqueue a plurality of events, an event handler programmed to process events in the event queue, and a thread pool coupled to the event handler. A resource manager further can be coupled to the thread pool and the event queue. Moreover, the resource manager can be programmed to allocate additional threads to the thread pool where a number of events enqueued in the event queue exceeds a threshold value and where all threads in the thread pool are busy.

Abstract: Access to a session between a remote computer and an application resident at a host computer connected to the remote computer is provided via a link object embedded in a Web page accessible at the remote computer. A session is established between the remote computer and the application, and a link object associated with the established session is embedded in the Web page in response to establishment of the session. In response to termination of a session, the link object associated with the terminated session is removed from the Web page. According to another aspect, user selection of the link object associated with the established session is accepted at the remote computer. In response, a user interface to the established session, e.g., an input/output “screen,” is provided at the remote computer. According to another aspect, a host access web page is accessed to establish a session.

Abstract: Sessions with a host-based application are managed by embedding a user interface, such as a screen, for a first session between the remote computer and the application in a Web page displayed at a remote computer. Preferably, a Java applet is downloaded to the remote computer and processed to embed the user interface. The downloaded Java applet may also be processed to establish the first session between the remote computer and the application. Upon termination of the first session, the user interface is removed from the Web page. According to one aspect, a link object for accessing a second session between the remote computer and the application may be embedded in the Web page and, upon embedding the user interface for the first session in the Web page, the link object may be removed from the Web page. Upon termination of the first session, the user interface for the first session may be removed from the Web page, and the link object for the second session embedded in the Web page again.

Abstract: A session is conducted with an application resident on a host computer by loading terminal information at a computer, operatively associated with the host computer and which is part of a network including a plurality of resource locations, from a host access resource location of the plurality of resource locations. The terminal emulation information is processed to conduct a session between the computer and the application. A resource location of the plurality of resource locations is then accessed from the computer while the session persists. The terminal emulation information may be downloaded to the computer from a server of the network. According to one aspect, a common environment capable of being produced under a plurality of different computer operating systems, e.g., a Java environment, is produced at the computer. The terminal emulation information is processed under the common environment to thereby conduct a session between the computer and the application.