NUT 3.0 & new architecture

This is a sandbox to lay down all ideas and considerations NUT 3.0, and shape up a specification:

Architecture considerations

1) C++ transition for the core (in parallel of the classic / historic core)

• new drivers (nutdrv_*, external mapping, thread-safe code in libs, main.cpp loader / "empty shell", callbacks with real interface (not void/void))

• nutdrv-controller

• nutd

• nutmon

• nut-client

• …​

2) asynchronous communication from end-to-end (use MQ)…​ energy efficient SW

• needs UML diagrams (flows, class, …​)

Sandbox

• Source tree reorganization

• Naming transition

  • nutd, with multiple back-end plugins (classic, dbus, MQ / MQTT, Upower, SNMP, …​)

  • drivers renamed to nutdrv-*

  • clients merged into nut-client

• Roadmap