FluentConnection class refactoring will help towards the work of making PyFluent flexible to support REST in addition to gRPC connectivity.
FluentConnection covers many concerns. A clue that this is so is the almost twenty construction arguments.
Fluent's PyConsole switches off gRPC connectivity by passing in channel='' which is consistent with the fact that the concept of gRPC connectivity is (incorrectly) embedded in FluentConnection itself, rendering it less flexible. Note that channel='' is itself a bug waiting to explode and that the FluentConnection constructor does not properly handle such irregular inputs.
We should address this early in the task to allow PyFluent to support REST. I will add more details later.
@prmukherj @mayankansys
FluentConnectionclass refactoring will help towards the work of making PyFluent flexible to support REST in addition to gRPC connectivity.FluentConnectioncovers many concerns. A clue that this is so is the almost twenty construction arguments.Fluent's PyConsole switches off gRPC connectivity by passing in
channel=''which is consistent with the fact that the concept of gRPC connectivity is (incorrectly) embedded inFluentConnectionitself, rendering it less flexible. Note thatchannel=''is itself a bug waiting to explode and that theFluentConnectionconstructor does not properly handle such irregular inputs.We should address this early in the task to allow PyFluent to support REST. I will add more details later.
@prmukherj @mayankansys