Re: com php-src: Going to refactor mysqlnd: ext/mysqlnd/mysqlnd.c ext/mysqlnd/mysqlnd_alloc.c ext/mysqlnd/mysqlnd_bt.c
ext/mysqlnd/mysqlnd_wireprotocol.c ext/pdo_mysql/mysql_driver.c
| From: | Pierre Joye | Date: | Sun, 18 May 2014 07:20:39 +0000 |
| Subject: | Re: com php-src: Going to refactor mysqlnd: ext/mysqlnd/mysqlnd.c ext/mysqlnd/mysqlnd_alloc.c ext/mysqlnd/mysqlnd_bt.c ext/mysqlnd/mysqlnd_wireprotocol.c ext/pdo_mysql/mysql_driver.c |
||
| References: | 1 2 3 4 5 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-78432@lists.php.net to get a copy of this message | ||
On Thu, May 8, 2014 at 8:27 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> I suppose the most trickiest part will be in the situations where
>> mysqlnd plays with the reference counter to skip memory copies. However
>> recently in 5.6 we added a second mode which doesn't reference but
>> copies data, which is probably what phpng will want from mysqlnd, right?
>
> I would assume since phpng is all about performance we'd actually want
> mysqlnd to avoid copying.
If you agree I will make it at least build smoothly and see how it
goes. Re-factoring to actually benefit from phpng new design can be
done in a 2nd step. Thoughts?
It will also help the windows support, which do not support libmysql
anymore (we are thinking to allow Mariadb client at some point but
this is a secondary priority.
--
Pierre
@pierrejoye | http://www.libgd.org