How to make the app whose GUI is separated from the engine

buddhist · Post by **buddhist** » Tue Feb 06, 2007 2:16 pm

If I need to design an application whose GUI can completely run in a separate process and the actual engine runs in another process, generally what architecture I need?

Looks like I have to conceive a communication protocol for GUI and the engine. All data should be cross-processes, hmm? If there is much data, it would be really bad. Then how to?

FlyingIsFun1217 · Post by **FlyingIsFun1217** » Tue Feb 06, 2007 3:08 pm

Hard to tell exactly what you want separated from the GUI, but your best bet (from what I can tell) would be to create the gui, and have it use a .dll file to access all of the code for... whatever it does...

FlyingIsFun1217

Ryan Wilcox · Post by **Ryan Wilcox** » Tue Feb 06, 2007 3:16 pm

wxWidgets provides interapplication communication tools

buddhist · Post by **buddhist** » Wed Feb 07, 2007 1:02 am

My idea is that I need my app GUI has ability of running in an independent process, and the core logic could run in another process without GUI, for purpose of high performance. For example, it would run like a remote debugger.

FlyingIsFun1217 · Post by **FlyingIsFun1217** » Wed Feb 07, 2007 1:43 am

See Ryan Wilcox's post then.

FlyingIsFun1217

krzysiek_t · Post by **krzysiek_t** » Thu Feb 22, 2007 12:02 pm

It sounds like perfekt place to use remote method invocation parading. Take a look at CORBA or something similar.