You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the MVP and 1.0 release we updated the protocol from 3.0 to 3.5. This was not arbitrary as we wanted SHA512 authentication support. Now we need to make the next jump from 3.5 to 3.11. This along with some work on the server that will be done to enable complex types in drivers outside of the JDBC will give us the opportunity to implement complex type support in the node driver when the time comes. Other significant protocol changes that will need to be handled from this move is client backward compatibility, UUID support, and OAuth 2.0 should we implement OAuth in the node driver as well.
The text was updated successfully, but these errors were encountered:
This will be done in parts. The first PR should come shortly and cover the protocol upgrade from 3.5 up until the version before complex type support. We are planning on implementing complex type support not immediately, but soon, and at that time the protocol will be upgraded to 3.12, or 3.13 etc if it has been updated again.
DMickens
changed the title
Protocol Upgrade from 3.5 to 3.11
Protocol Upgrade from 3.5 to 3.12
Oct 6, 2022
For the MVP and 1.0 release we updated the protocol from 3.0 to 3.5. This was not arbitrary as we wanted SHA512 authentication support. Now we need to make the next jump from 3.5 to 3.11. This along with some work on the server that will be done to enable complex types in drivers outside of the JDBC will give us the opportunity to implement complex type support in the node driver when the time comes. Other significant protocol changes that will need to be handled from this move is client backward compatibility, UUID support, and OAuth 2.0 should we implement OAuth in the node driver as well.
The text was updated successfully, but these errors were encountered: