Abstract
The X Protocol represents the first major deviation from the existing client/server protocol in MySQL. The X Protocol is designed to be extensible, maximize security, and ensure good performance. All three of these categories were at the top of the list for must-have features and requirements when the X Protocol was designed.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Then, why is it MySQL 8 and not MySQL X?
- 2.
A worklog is an internal document used to capture design and requirements for implementing features in MySQL.
- 3.
An evolution of SSL: https://en.wikipedia.org/wiki/Transport_Layer_Security .
- 4.
A framework for authentication and data security: https://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer .
- 5.
Asymptotically successful at best; there’s always a fly in the ointment somewhere.
- 6.
In other words, place your chair in a semireclined state, put on your favorite music, and make sure plenty of your favorite beverage is near at hand.
- 7.
Or as I am sometimes accused of “not leaving things well enough alone.” Guilty. I’ve been taking things apart since I was a child. And sometimes I’d put them back together!
- 8.
In SQL terms use it.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Charles Bell
About this chapter
Cite this chapter
Bell, C. (2018). X Protocol. In: Introducing the MySQL 8 Document Store. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2725-1_7
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2725-1_7
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2724-4
Online ISBN: 978-1-4842-2725-1
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books