Re: Bundling "modern" extensions
| From: | David Muir | Date: | Tue, 07 Jun 2011 09:32:57 +0000 |
| Subject: | Re: Bundling "modern" extensions | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-53120@lists.php.net to get a copy of this message | ||
On 07/06/11 15:49, Reindl Harald wrote:
>
> Am 07.06.2011 04:42, schrieb Martin Scotta:
>> On Mon, Jun 6, 2011 at 8:15 PM, Reindl Harald <h.reindl@thelounge.net>wrote:
>>
>>> Am 06.06.2011 23:40, schrieb Martin Scotta:
>>>
>>>> It'd be very nice if some extension could be enabled just by dropping the
>>>> "extension file" on the path.
>>>> So developers can check what they have using phpinfo, and then upload the
>>>> needed extension using ftp. Is it possible?
>>> if a "developer" only would try such idiotic action
>>> he would lost his accounts forever and get fired from
>>> one day to the next!
>>>
>>> WTF how can anybody have the idea that it would be a good
>>> idea to let non-sysadmins uplod and execute binaries on a
>>> server?
>>>
>>>
>> Thanks you for all yours responses.
>> Now it's clear what the issue is... the usage of compiled "libraries".
>>
>> We need some middleware between the core and PHP.
>> That way extensions could be written in PHP, compiled and distributed in
>> some "library" format.
>> Library users just add them into their path, include them, and use the
>> classes/functions as usual.
>>
>> - No OS dependence
>> - minimum dependence with core version
>> - size of core will reduce drastically
>> - faster runtime, include only what libs you use, as you need them
> what are you speaking about and since how long you are working
> with PHP that you never heard about PEAR, ZendFramework....?
>
And you should know that PEAR and ZF are user-land libraries, not
compiled libraries.
I think Martin is wishing for is the PHP Native Interface:
https://wiki.php.net/rfc/php_native_interface
Either that, or a PHP equivalent of Cython or Pyrex.
Cheers,
David