On Thu, 06 Dec 2001 10:52:19 +0000, Simon Oliver wrote: >This problem with Apache killing processes when the client stops >comminucating applies to more that just DBI. This is a more general >question and you will probably get better support on one of the >comp.perl.* mailing lists.
I think you mean newsgroups AKA usenet, and <comp.lang.perl.*>. But perhaps the CGI newsgroup is a better choice: <comp.infosystems.www.authoring.cgi>. But anyway, perhaps even bringing this back on track for the DBI mailing list... The approach I usually take is a fork, let the child close its STDIN and STDOUT, and let the parent terminate normally with a normal info web page. This is "if I recall correctly", Randal Schwartz has used this approach a few times in his WebTechniques columns, which are online at <http://web.stonehenge.com/merlyn/WebTechniques/>. You can search in the listings. Column 20, "search in progress page", looks like it uses this technique. The problem for DBI is that if you open the DBI connection first, and then fork an lety the parent terminate, that then the connection will likely be severed for the child too. You probably *want* to check for a valid connection before showing a "processing..." page. So, how do you get around that? The DBI does say to use "InactiveDestroy". It also says that "some databases, including Oracle, don't support passing a database connection across a fork". Solutions? -- Bart.
