Julio,
Thanks for taking a stab at it. I should have been more clear, I mean when workers are killed. I do this from within the worker to try and have an orderly shutdown. Your reading of the docs is correct though. Workers are a thread of execution, like any other process, but 4D has its own magic loop waiting for incoming 'messages'. These messages aren't really messages, they're blocks of code that are appended to the worker's thread of execution and then run through EXECUTE. At least, that's how they behave. ********************************************************************** 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] **********************************************************************
