On 10-9-2015 09:29, Alex Peshkoff wrote: >> I am not specifically talking about saving packets. The assumptions and >> requirements of the new authentication protocol handshake are - as far >> as I know - not documented in structured manner except in the code >> itself. When I get it a bit cleaned up and working in Jaybird I'll do my >> best to add it to the existing wire protocol doc. > > That will be a real breakthrough for interbase/firebird protocols - as > far as I know there never used to be such docs.
It already exists, although it is a bit sparse and doesn't contain everything, see src/docs/firebirddocs/wireprotocol.xml in the manual project in CVS. It was started by Carlos Guzman Alvarez when he was working on the .net provider, and I have added some more info when I was working on the V11 and V12 implementation in Jaybird. >> >> For a non-C++ programmer the Firebird code can be a real maze when >> looking for where things are defined and how they are defined and how >> things go together (as an example: ClntAuthBlock is implemented >> partially in remote.cpp and interface.cpp); > > I know it's a bad way - but it was a simplest one to avoid unresolved > externals in both client & server at the same time avoiding inclusion of > too many unneeded code at both sides. > >> I need to keep switching >> between remote.cpp, interface.cpp, and inet.cpp > > Feel lucky that you do not deal with windows - there are also xnet & > wnet in it ;) True ;) Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
