Re: Multithreaded application freezing



hi;

On 2 February 2015 at 22:07, G Hasse <gorhas raditex nu> wrote:
Den 2015-02-02 22:57, Gulshan Singh skrev:

I strongly advice designing an application in this way.  Every window in an
application should be a separate process. Between processes you should
find a good protocol. This protocol should be transported over some message
buss. (example: www.spread.org)

there are loads of issues with a design like that.

you're going to overengineer your application, and then have issues
whenever you have to context switch between processes because you
moved from a window to another one inside your own application.

you'll have to ensure all your shared data structures are copied
correctly across process boundaries, and you'll have to have proper
bookkeeping to ensure processes do not end up using old data.

you won't be able to fork() and build your UI in a child: that's not
how X11 (or any other windowing system, really) works. you'll need to
spawn a new child process from a server.

it's not that you cannot do it. it's that you're overcomplicating any
design in a way that rapidly explodes the maintainership overhead of
your project.

ciao,
 Emmanuele.

-- 
https://www.bassi.io
[ ] ebassi [ gmail com]


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]