I may be missing your point Patrick - but your comment re persistence of CGI jobs is not correct.
What you _can't_ control without going the persistence route is whether you get connected to the _same_ instance of a program because your request may be allocated to a different thread.
you can also have a pre-start job that just runs its own sockets interface - for example. Any non-interactive job can be restarted and will persist as will the state of the programs running within them unless you take actions to have them terminate.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.