John Lister wrote:
> The extended protocol stuff has been
> bolted subsequently to the execute part of the driver rather than doing
> it when the query is prepared...
That was indeed what happened (slightly more than "bolted on", there was
a rewrite of the network layer!), but remember that the driver actually
supports both v2 and v3 protocols. There are fewer cases that need v2
support these days, but I'm sure there would be some unhappy people if
the driver suddenly dropped it altogether. So keep in mind that any
architectural changes will still need to support v2 as well at this stage.
-O