mod_cluster 2.0

Overall

• Create two separate repositories within modcluster organization: mod_cluster-balancer and mod_cluster-worker or perhaps mod_cluster-modules and mod_cluster-libs ...
• The aforementioned depends on project renaming
• Use NOE TS to run CI on both Java and Native code for both aforementioned repositories with Apache's latest stable
• Finish modcluster.io
• Documentation
• Downloads
• Nightly latest builds (including native modules) for Windows and Linux
• Finally push forward a new re-engineered RPM to Fedora (23, 24, rawhide)
• Protocol versioning

Java libs

• Move to nonblocking I/O (multicast logic)
• Drop legacy versions (e.g. sar)
• Tomcat 9/8.5 support (already wip)

C libs

• Add CMAKE support and gradually steer away from Autotools
• Move the C code to ASF?
• Remove the slotmem code and use the httpd-2.4 code
• Arrange the mod_proxy_cluster to be a simpler loadbalancer
• Remove copy of mod_proxy code
• Remove legacy and unused code:
• old httpd servers
• Jgroupsid -- if we decide to put it back, we always could
• Refactor parser logic into a separate file handling MCMP + versioning
• Refactor code style and legacy warnings and typos -- in other words, "it works, don't touch it" doesn't hold for 2.0-SNAPSHOT
• Open the doors for new features and ideas:
• httpd+wsgi acting as mod_cluster workers? ...and more off the hook stuff