Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66609
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hristov.com from 91.196.124.214 cause and error)
Message-ID: <5141997B.9070004@hristov.com>
Date: Thu, 14 Mar 2013 10:33:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAEe4Dn8hubM3SmM99AENQmGm6KG7m5ty5MqK3w-VQ4Emz-wT0Q@mail.gmail.com> <5140E399.905@lerdorf.com> <CAEe4Dn-bA+Qv+YbEiGRH42uQ6gWBgtDVnwVS8R1ED=QXGm7A0g@mail.gmail.com>
In-Reply-To: <CAEe4Dn-bA+Qv+YbEiGRH42uQ6gWBgtDVnwVS8R1ED=QXGm7A0g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] idea: add wrapper support to mysqli_connect
From: php@hristov.com (Andrey Hristov)

  Hi,
On 03/13/2013 10:09 PM, Thomas Anderson wrote:
> On Wed, Mar 13, 2013 at 3:37 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>> On 03/13/2013 12:08 PM, Thomas Anderson wrote:
>>> Instead of passing localhost to mysqli_connect as the $host parameter
>>> I think it'd be useful if you could pass something like
>>> ssh2.tunnel://user:pass@example.com:22/192.168.0.1:14 to it as well.
>>>
>>> The main advantage I see of doing that is that you could tunnel
>>> through SSH2, through SOCKS, through HTTP CONNECT, etc, a lot more
>>> easily than you currently can. Like you could have an SSH connection
>>> re-created every time a PHP script is called and a tunnel dynamically
>>> made instead of having a persistent tunnel created with autossh or
>>> whatever.
>>>
>>> And even if SSH2 / SOCKS / CONNECT don't exist as built-in wrappers
>>> custom stream wrappers could be made. This would additionally make it
>>> easy for people to examine the underpinnings of MySQL. Instead of
>>> intercepting the packets the MySQL client sends out and placing them
>>> into an SSH tunnel or whatever one could just dump them to a log file
>>> to better understand how MySQL clients work internally.
>>
>> Instead of adding all that gear to PHP itself, wouldn't it make more
>> sense to just use something like autossh to maintain your ssh tunnel and
>> have PHP connect to your tunnel endpoint? mysqli_connect() in PHP is
>> just a thin wrapper on top of the underlying library.
>
> Oh - I didn't know that. I thought (hoped) it might have been like a
> two second code change lol.
>

a very easy way is to write a mysqlnd plugin that overwrites 
mysqlnd_connect, maybe some small changes to mysqlnd_net. You can pass 
whatever you want and it will connect the way you want. At the end there 
should be opened PHP stream. Upload it to pecl.php.net and let the 
people use it. If many people decide to use it it might get its way into 
the core of mysqlnd.

Best,
Andrey