Re: Re: com php-src: Address feature request #38917 for native SPKAC (HTML5 keygen element) support: ext/openssl/openssl.c ext/openssl/php_openssl.h
ext/openssl/tests/openssl_spki_export.phpt ext/openssl/tests/openssl_spki_export_ch...

From: Date: Sat, 11 May 2013 22:18:44 +0000
Subject: Re: Re: com php-src: Address feature request #38917 for native SPKAC (HTML5 keygen element) support: ext/openssl/openssl.c ext/openssl/php_openssl.h
ext/openssl/tests/openssl_spki_export.phpt ext/openssl/tests/openssl_spki_export_ch...
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi!

> I'd to disagree. Besides the lack of testing (openssl is stable, or do
> we begin to say feature a is not and feature b is beta but everything
> else is stable?), the nightmare about what is available in which
> version is really not what we should do.

Where's the "nightmare"? Each function is tagged with available version.
Waiting for several years for a new function is not a good idea.

> php-next will be in a year, openssl can be released in pecl as well.
> There are many requests supporting this idea, incl. from <5.5 users,
> incl. 5.3.

"Can be released" and actually released are two very different things.
If we have somebody who commits to actually releasing it, with time
table, etc. that would be different story. Even then, with your model it
means we'd be re-releasing every extension as PECL...
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227


Thread (11 messages)

« previous php.internals (#67400) next »