is "code injection" even a problem? preemptive mode is all about multi-tasking.
I would expect minimal communication between those tasks, literally, they should be "preemptive". it's true you can start a preemptive process with CALL WORKER, but that is not required, you can also use New process or Execute on server. it's totally fine to have a runaway preemptive task. workers, on the other hand, is all about messaging. it's a different way of cooperating compared to cooperative processes, that is, they is not "manager (scheduler)" or concept of "yield (IDLE)", nevertheless, process are expected to cooperate and not preempt. maybe it's better not to consider the two features as a set. 2017/05/07 11:20、David Adams via 4D_Tech <[email protected]<mailto:[email protected]>> のメール： I'm looking at preemptive mode again and, again, tried something I wondered about. "What happens when you inject bad code?" Say you've got a preemptive thread, it can't use MESSAGE. If you put MESSAGE in the call chain, the Compiler complains. Go the Compiler! But what happens if you have a method that calls MESSAGE: ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
