Related wrinkle....I'm now wondering about something else: Does KILL WORKER completely kill a worker, or does it sometimes just hurt it really, really badly? I have been working under the assumption that when KILL WORKER completes, that the worker is *totally* gone. Meaning, no process-level values (variables, etc.) remain anywhere.A worker can be restarted very quickly after being killed. It gets the same name (workers have unique, case-sensitive names, outside of buggy situations) - but the contents should be blank. At least, that's what I think and what would be best. Web processes, as an example, do *not* work like this - they stay alive for a few seconds and may get reused. New process *does* work like this. Let a process finish and restart a fresh version and you get a blank slate.
I suspect with workers that they normally die completely when killed, but not always. I've just reread the docs and they don't address this point explicitly. This is the sort of question I tried using the Forums to get answered and, frankly, I didn't get answers. So, I'm going to have to go with the assumption that a new worker *may not be virginal.* There may be some gunk hanging around form an earlier incarnation of the worker. This is only relevant if you use KILL WORKER, but that's a standard command. Does anyone know anything more about this that could help change some of my speculations into information, one wary or another? ********************************************************************** 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] **********************************************************************
