Re: cvs: php4 /ext/standard file.c
| From: | Sascha Schumann | Date: | Sat, 23 Dec 2000 15:34:49 +0000 |
| Subject: | Re: cvs: php4 /ext/standard file.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-3273@lists.php.net to get a copy of this message | ||
> Most module will simply display it as an error as well, if they
> handle it at all. So worst case - we'll be overriding their
> error reporting function, or they'd be overriding ours. No
> biggy in both cases.
Our handler would somehow have to be able to restore the
context to a defined state (i.e. to reenter the main Apache
loop and to cleanup the left-overs of the other module). How
would a PHP handler achieve that?
> (d) If you think that it's still likely we'll interfere with the core
> behavior of other modules, we can always turn on our signal trapping on
> request startup and restore the original signal handle on request
> shutdown. I don't think it's necessary though.
That sounds like a very expensive operation.
- Sascha