Thanks for the clarification. As I understand it, the syntax on the client end
is to use "." as the host name.
I was using "localhost" on the LAMP configuration, and never bothered to
change it. With 7 or so web-based users, there isn't much rush.
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
>From: Shawn.Green@stripped [mailto:Shawn.Green@stripped]
>Sent: Monday, February 01, 2010 11:07 AM
>To: Jerry Schwartz
>Cc: 'Wagner Bianchi'; mysql@stripped
>Subject: Re: WAMP vs LAMP
>Jerry Schwartz wrote:
>> From: Wagner Bianchi [mailto:wagnerbianchijr@stripped]
>> Sent: Thursday, January 28, 2010 2:03 PM
>> To: Jerry Schwartz
>> Subject: Re: WAMP vs LAMP
>> [JS] The file paths were all the same, actually, and the address for MySQL
>> [WB]Consider to use MySQL on Unix like environment because the socket file.
>This way you will get more performance then use TCP/IP on MS Windows.
>> [JS] That's an interesting suggestion. Windows has socket files, but I've
>never looked at them. In fact, I don't even know if MySQL can us a socket
>and TCP/IP at the same time. We're going to have more ODBC traffic than web
>traffic, I expect.
>On Windows they aren't called "sockets", they are "named pipes" and yes
>you can be listening to both internal and external connections at the
>When connecting locally, you have both options at your disposal
>There is even another option for Windows, --shared-memory
>This works similar to a named pipe and if you want to enable both (pipes
>and shares) at the same time, you need to provide different names. The
>TCP/IP ports are independent and also available.
>Shawn Green, MySQL Senior Support Engineer
>Sun Microsystems, Inc.
>Office: Blountville, TN
>MySQL General Mailing List
>For list archives: http://lists.mysql.com/mysql
>To unsubscribe: http://lists.mysql.com/mysql?unsub=1