How not to hard-code the handler priorities?

MBassador is used to define application extension point in the developing framework. The framework sends a context to listeners as a message, and listeners take the proper actions: alter it, skip it, log it or ....

I think it's nice if I could give the end user a chance to reorder the priorities at runtime, or maybe with a config file, before I publish this thing to github. Is it possible?

I think I missed it: #58, is it possible to provide a custom Comparator for handlers priority? gotta read the docs again.

[bennidi]

This feature could definitely be implemented using a custom comparator but there would need to be a way to tell the bus how to pick and apply that comparator.

A message publication first collects all SubscriptionS that match the message type, then orders them (currently according to their priority index), then invokes each of them with the given message.

Maybe you feel like creating a PR on this one...?!