List of channels not working together or that aren't tested yet

Strategies not working together

Strategy 1	Strategy 2	Description
DirectBroadcastRouting	GMSOrder	GMSOrder requires nodes to send messages as publish messages to a dedicated root node where messages are ordered, but DirectBroadcastRouting sends every message directly to its subscribers and every node is a root itself
HierarchicalSpreaditRouting	GMSOrder	GMSOrder requires one dedicated root node to send notify messages down the tree, but in HierarchicalSpreditRouting the message is propagated upwards the tree and every node notifies its childs without going over a root node
DirectBroadcastPartition	GMSOrder	Not sure whether its because of the dynamic partitioning or because of every node being root on a tree
DirectBroadcastPartition	DirectBroadcastRouting	It's not an invalid combination, but it produces a lot overhead compared to strategies with the same routing behaviour. If you need something like that choose DirectBroadcastPartition with DirectRouting or NullPartition with DirectBroadcastRouting. Both combinations will send messages directly from node to node without any overhead through a root node while using n subscriptions where n is the amount of nodes, while this combination would take n^2 subscriptions.

Strategies not tested right now

Strategy	Description
All FilterStrategies	Implementation wasn't ever fully tested and former developer isn't available, so we have to check it on our own which means we need to read the thesis for this topic

Notes

Actually using multiple channels can cause some synchronisation problems and a message overhead during channel synchronisation in startup of m2etis. It's recommended to use just a few channels for now. This problem will be addressed in version 0.5.