c - Managing resources allocated by client processes -
As part of an experiment, I want to write an OpenGL-based UI server for applications like X11 Or in the composition of quartz: Core project presents objects in a single viewport, but all graphical objects are being controlled by remote processes.
The idea is that the idea stability is only dependent on the core process, if the client processes the segfalts, its allocated resources will be safely freed - a need for that facility is safely finding out whether Whether the client process has crashed or not.
What is the best practice here?
I think this should be known as an event in relation to the client, like any other Architecture with Client / Server
If you use sockets, the socket will eventually register that the one side has closed the socket (the process crashes, the end of the socket will stop), and you can detect it View server records in owner's clientele, and clear all resources.
It will be very strange for the server directly (process ID or whatever), and also the limitless limit your architecture is run locally, and not on a network.
Comments
Post a Comment