-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Development Ideas
http://dev.mysql.com/doc/internals/en/connection-phase-packets.html#packet-Protocol::HandshakeResponse41 http://dev.mysql.com/doc/internals/en/capability-flags.html#flag-CLIENT_CONNECT_ATTRS
- .mylogin.cnf http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html
- SHA-256 http://dev.mysql.com/doc/refman/5.6/en/sha256-authentication-plugin.html
- auth_socket http://dev.mysql.com/doc/refman/5.6/en/socket-authentication-plugin.html
Network Compression Mode (Issue #24)
Currently, we send request packet, then receives response packet.
Since Go doesn't provide efficient way to nonblocking EOF check, we may send request packet even if server closed the connection already. Sending request on already closed connection makes ErrBadConn unsafe. If we can detect EOF before sending packet, we can ErrBadConn safely.
Using separated goroutine to read from connection is Go's normal way for it. Reader goroutine may be required to implement Context support too (#496).
There may be significant performance regression. But I think we should do it.