In my mind, I think the process-chain would look like this:
The spawned listener that is "using" 10400, does all the communication.
The main process, gets polled by the child. Meaning the child is "dumb";
All access to the INI/DB is handled by the master pid.
The master process has the ability to spawn new processes depending on if the child becomes "stuck" during comms, since it grabs the first initial comm.
Or, you could have one process doing the handoffs of data, and one listener - since you will have "low amounts of data" passing over.
What I am aiming at is separation of ownership and what data is servered by what pid.
This could mean, that for the low end segment that uses a INI, you need one engine, and for the SQL-driven, you have another. But, the listening service/child remains the same as it handles the same kinds of data.
Sadly, I have no idea how to do any of this with KF ;).
Edited by Björn (2013-12-24 11:13 AM)
_________________________
as long as it works - why fix it?
If it doesn't work - kix-it!
