Hi all, the replication point is a good one, I did not think about that. However, I still believe that on the road to v6 adoption, databases are far from being our most pressing roadblock.
Thanks all! Carlos On Fri, Oct 22, 2010 at 4:52 PM, Jerry B. Altzman <jba...@altzman.com>wrote: > Only to you. > on 10/22/2010 10:02 AM Carlos Martinez-Cagnazzo said the following: > > IMHO you should never, ever make your MySQL accesible over the public >> Internet, which renders the issue of MySQL not supporting IPv6 correctly >> mostly irrelevant. You could even run your MySQL behind your web backend >> using RFC1918 space (something I do recommend). >> > > Except for those of us who have to support applications based upon MySQL > replication...in that case, we use IP-based access rules on a firewall in > front, and on the host, and on the MySQL server itself. But we still need IP > access to it. > > We could shade it all by using IPSec or VPN tunnels, but that's more > administrative overhead, and MySQL replication is fragile enough without > adding that. > > > Moreover, if you need direct access to the engine, you can trivially >> create >> an SSH tunnel (You can even do this in a point-and-click way using the >> latest MySQL Workbench). SSH works over IPv6 just fine. >> > > See above about replication. > > Carlos >> > > //jbaltz > -- > jerry b. altzman jba...@altzman.com www.jbaltz.com > thank you for contributing to the heat death of the universe. > -- -- ========================= Carlos M. Martinez-Cagnazzo http://cagnazzo.name =========================
