gquentin/coolfluid3 — comment on commit 747066002ae61eaa2100a8343ddcae165fe6da59
File:  line 0
By gquentin:

I'm currently trying to cleanup the server code. In my opinion (and according to the current architecture) the server should only be a network layer for COOLFluiD that forwards requests (boost signals) to the MPI workers (coolfluid-solver). This way, I think the server doesn't need those dependencies because it never uses them. The MPI workers do, and they still depend on CF3_KERNEL_LIBS so it should still be OK because the component tree is managed by the workers now ;)

In my mind, the server should be implemented through one class (the network part) and an additional file for the main().

I might be wrong by removing those dependencies, but this commit is a part a big work which will _in fine_ remove Qt from the server. For now the main Qt part of the server is the network...and I'm learning Boost.Asio to remove this one :)

So don't take this commit as is. I will rewrite a big part of the GUI stuff in the following weeks in order to only depend on Qt when needed (the graphical part) and redesign the GUI core (that manages the network, threads and components on the client side) to provide an API that would allow a contributor to write it's own user interface (command line, iPhone or Android app, etc..). This new API would abstract the remote access to the simulation and let the developer to only concentrate himself on the user interaction part. The current API is not generic enough in my opinion for that.

Maybe I'm dreaming to the wrong direction, the future will tell us that. Sometimes I have utopian ideas...especially at 1:00 AM :)