This software enables callback dispatch for session events.
The POE::Session::MultiDispatch module is an excellent replacement for POE::Session with callback dispatch functionality for POE sessions. This module adds the ability to associate multiple handlers with each event and control the execution order by extending the interface of a POE::Session. POE::Session::MultiDispatch is built on POE::Session as a base class.
Compared to POE::Session, only the last callback survives when multiple callbacks are registered for an event, while all others are clobbered. POE::Session::MultiDispatch keeps all registered callbacks in the order they were defined and executes them in that same order when an event triggers. This behavior holds unless there is any modification to the order.
The order in which the inline_states, package_states, and object_states are called is not documented; however, it's unlikely that it will change. It is essential to know what you're doing if you intend to care too much about the order.
All the real heavy lifting is still done in POE::Session, and the interface is precisely the same except for the following additions. For more details on POE sessions, please refer to the POE::Session documentation.
The SYNOPSIS of the module includes creating a POE::Session::MultiDispatch session and using callbacks with the help of _start, first, last, and stop methods. Overall, the POE::Session::MultiDispatch module is an excellent addition for users looking to add more control over the order of execution and keep track of registered callbacks.
Compared to POE::Session, only the last callback survives when multiple callbacks are registered for an event, while all others are clobbered. POE::Session::MultiDispatch keeps all registered callbacks in the order they were defined and executes them in that same order when an event triggers. This behavior holds unless there is any modification to the order.
The order in which the inline_states, package_states, and object_states are called is not documented; however, it's unlikely that it will change. It is essential to know what you're doing if you intend to care too much about the order.
All the real heavy lifting is still done in POE::Session, and the interface is precisely the same except for the following additions. For more details on POE sessions, please refer to the POE::Session documentation.
The SYNOPSIS of the module includes creating a POE::Session::MultiDispatch session and using callbacks with the help of _start, first, last, and stop methods. Overall, the POE::Session::MultiDispatch module is an excellent addition for users looking to add more control over the order of execution and keep track of registered callbacks.
What's New
Version 1.3: N/A