|
Expresso 5-5-0 | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Interface Summary | |
| AsyncProcess | Interface for a process that is to be completed asynchronously while other things in the Expresso system goes on. |
| AsyncProcessor | The AsyncProcessor is the entity that actually does the processing of the AsyncProcess objects. |
| AsyncProcessResult | AsyncProcessResult a wrpper interface for what is handed back to the client when a process is waiting, running, or completed.. |
| AsyncTicket | Opaque object. |
| Class Summary | |
| AsyncServlet | This is a default way to initialize the async process factory. |
| DefaultAsyncProcessor | This is a default implementation of the AsyncProcessor. |
| DefaultProcessResult | This is a default bean implementation of an AsyncProcessResult. |
| DefaultTicket | Default implementation of the AsyncTicket. |
| ProcessorFactory | Processor Factory. |
| ProcessThread | |
| Exception Summary | |
| QueueFullException | Queue full exception occurs when the async process processor has too many jobs waiting for it. |
Async processor framework.
The Async processor framework is designed to handle situations where an Expresso Job is not appropriate because you do want the results sent back to the user when it is done. Instead, the AsyncProcessor queues items up and processes them as fast as it can sending status and result objects back to the "Ticket Holder" when status is requested.
See the EDG chapter on Async Processing for a more detailed description of the purpose of this package.
|
Expresso 5-5-0 | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||