|
| Session Details | |
| |
|
| |
|
| The asynchronous I/O API supports the development of event-driven applications that use the Proactor pattern. It integrates the demultiplexing of I/O and completion events with dispatching to application-provided handlers that consume the result of I/O operations. In brief, an application initiates an I/O operation and specifies a completion handler that is invoked when the I/O is complete. This session contrasts this with the existing API that supports the development of event-driven applications that use the Reactor pattern. With the existing API, a selector is used to multiplex channels to receive events when the channel is ready for I/O. The session presents lessons learned in implementing a highly scalable AIO-based server and describes how AIO was implemented inside the Project Grizzly framework. |
|
| |
|
| |
|
| |
|