Major Description
The order element specified when inserting a handler only allows for at most one "before" and one "after" handler. I currently have a case wherein two handlers ought to be run before a third, and this proves problematic for the system as implemented.
If my system relies on both A and B coming before C and D, there is no direct way to state this dependency. While an order might be imposed, an artificial order containing false dependencies is less than ideal and requires more configuration than direct specification.
This change could be accomplished in a backwards compatible manner by allowing the existing "order" element to have children, which identify additional "before" and "after" rules.