On 03/03/2016 12:26 PM, Mark Rotteveel wrote: > But my main concern > has to do with my experience with wire protocol changes in Firebird: > they are usually poorly documented,
Poorly is incorrect word here, remote protocol is not documented at all and (as far as I know) was never documented. Except comments in sources. > which creates a large burden on > driver implementers having to follow all intricacies of the code (in my > case in a language that I'm not fluent in) to understand what changes > they need to implement. Especially with code involving encryption or > compression, C++ code is not the most readable Worst is that it's still mainly C-code compiled using C++ and using some C++ features. But as long as it works full rewrite to C++ does not seem to be good idea. > when you have to > reimplement in a different language (or find the right library to do the > work for you). That is why I'm stressing that things need to be specced > and documented when it involves the wire protocol. I plan to write such document - unfortunately can't do it soon. But please do not expect hard protocol description regarding initial handshake - with various authentication and wire encryption plugins and related configuration settings (with encryption turned off less round-trips may be needed for handshake) such straightforward description of handshake protocol just can not exist. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
