Does anyone know or can they find out the following? What happens when workers die? 4D has at least two different approaches to this:
* HTTP processes wait before dying, but then die if there are no new requests after some time. (Or at least they used to.) Meaning, an HTTP process may or may not have old variables and so forth in place. * New process () / Execute on server () When they finish, they're dead. They're supposed to release file locks, record locks, etc. If you start a new copy of the process with the same name, it starts off in a "virginal" state. Which is it for workers? I thought it was like New process(), but am seeing evidence that it's not always the case. The docs aren't explicit. I take the implication to be that they should be fully dead, even if started almost instantly. But this doesn't seem to be true. The difference is pretty important. Is there a way to find out authoritatively? I've sent it to Wayne for tech support, so maybe that will work in time...but perhaps someone knows or has a shortcut to finding out? ********************************************************************** 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] **********************************************************************
