Re: Re[4]: [PHP-PEAR] Re: [phplib] Re: [PHP-PEAR] PHPLib and Pear merge
| From: | (Stig Sæther Bakken) | Date: | Mon, 12 Mar 2001 14:31:15 +0000 |
| Subject: | Re: Re[4]: [PHP-PEAR] Re: [phplib] Re: [PHP-PEAR] PHPLib and Pear merge | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-1800@lists.php.net to get a copy of this message | ||
[Maxim Derkachev <kot@books.ru>]
> Hello Stig,
>
> Monday, March 12, 2001, 12:35:42 PM, you wrote:
>
> SSB> Well, we'll just have to rewrite DB to C then (not kidding).
>
> Not the worst thing :) . But I'd rather bought Kristian's arguments
> concerning PHP appserver. The most overhead of such complex things
> like PEAR::DB is coming from its setup costs. There are many objects
> to be compiled, a lot of memory to allocate, and then this damn
> thing simply dies at the end of the request. I suppose it's not the
> right way to rewrite all the good things in C because they just need more
> time to compile.
> I didn't mean PHP is BAD because it is an interpreter.
I know you didn't. :-) A C rewrite would at least do away with the
compilation overhead, and add some execution speed. There are other
goodies that are only available in C too, such as object overloading.
I've started converting the PEAR base class to C while figuring out
the ins and outs of the Zend class API.
But I agree that an application server is needed. All that is really
necessary to make it happen is a SAPI implementation (similar to
sapi/servlet). With a few tweaks in the PHP build system we could
even put SAPI implementations in PEAR.
- Stig
--
Stig Sæther Bakken <ssb@fast.no>
Fast Search & Transfer ASA, Trondheim, Norway