What patterns for this application?
We have a large standalone C++ application which we are planning to port into java. Right now we are planning to port only the GUI (front end) part and retain the backend in C++ (Though, in the long long run we might even port the backend part to java but not right now). There are around 200 backend C++ programs.
In simple terms the general architecture/functionality of the current C++ application is like this.
Each front end screen will collects and passes the arguments to a common interface program
The common interface program writes the arguments into a flat file and invokes corresponding backend C++ program
The backend C++ program will read the arguments and generate an output file.
Later the front end will read the output file, parse and display it graphically.
If we want to retain the backend C++ programs for now, what is the general architecture that you would suggest and what Patterns should we consider to implement in the new version and how can they help?
Thanks
Raju
