Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

During this time it has been continually developed to meet the needs of production, research, and development sections.

...

  •  New features in version 5 will need to be validated by the Production section.
    To minimize the maintenance burden, unused features may be removed.
  •  It provides python 2.7 and Python3 apiAPI, to ease the testing process.
    There is no change in the python API, other than the addition of new features
  • The 4.X.X gui GUI is not interoperable with version 5 and vice versa.

...

  •  ecFlow 4.X.X series relied on boost serialisation for client-server communication,
     which meant sticking with a single version of boost, to maintain compatibility between versions.
    The ability to extend existing classes over the client/server divide was very limited
  •  ecFlow 5 has dropped the dependency for boost in the client/server comms , and now uses JSON.
    This means that future version versions of ecflow 5 can use different boost libs.
  • The latency during the client/server communication has been  been improved.

  • There was a requirement to use the older compilers to support RPM creation, this has been dropped. Ecflow 5 requires a minimum of c++14

    We now use the newer c++ compilers and features, resulting in improved performance.