|
|
Posted by Sanders Kaufman on 07/25/07 18:59
Rik wrote:
> On Wed, 25 Jul 2007 19:39:04 +0200, Sanders Kaufman <bucky@kaufman.net>
>> Their guys said that it would result in Zombie processes - something I
>> had to dig around to find out about - and I still don't fully
>> understand them. Since I'm still a loooong way from being a *nix
>> guru, I've been hyper-vigilant about not accidentally wasting a bunch
>> of resources.
>>
>> As it turned out, they were wrong. But, like Jerry, they were sooooo
>> adamant, it turned into a big broo-ha-ha and I've been a bit gun-shy
>> about 'em ever since.
>
> I could've told you they were wrong. Then again, this is quite clear in
> the documentation.
That's how it finally played out - with one minor exception.
At the time (I don't know if it's still true) there were two ways to
install PHP - MOD and CGI. In one, Zombies could gitcha. In the other,
they couldn't.
Here's the discussion and article on CNET:
http://articles.techrepublic.com.com/5100-22-1045433.html
Be aware when you read it that it was seven years ago, and although I've
got a lot to learn, I've learned a lot since then.
> Compare your current use of the constructor with people who used the
> string value of objects: it was an undocumented feature, and it came to
> bite them in the ass when things were changed.
Calling public functions, even constructors, is NOT an undocumented feature.
Indeed, after Jerry told me about how I *have* to *manually* call the
constructor, I RTFM'd and confirmed that he was right - that it's
*totally* apporpriate to call the manually call constructor.
> Just don't rely on anything db-wise to work later on in the script, so
> you should probably die()/exit() or redirect to create a somewhat nice
> degrade.
Using DIE this way is a great way to write a bad web application.
If your DBMS goes off-line, your users don't get a clean response.
They just get a blank page.
Navigation:
[Reply to this message]
|