On 09/04/13 18:11, Jim Starkey wrote: > So here's another seriously heretical thought. If you're planning for > Firebird to hang around another 27 years, it's time to define a modern > OO API that is easy to use from modern languages, is flexible and > extensible, supports an efficient remote protocol, and can fully support > the legacy SQL APIs as a proper client layer and maybe even BLR, if > that's still important.
That's what was done in FB3, except probably one point - what do you mean under 'supports an efficient remote protocol'? API is not _directly_ releated with remote protocol. In FB3 we kept remote protocol more or less (sooner more) as it was before. But new OO API, working with that protocol, was defined. SQLDA API is implemented as a layer over it (in FB3 - directly in yvalve, i.e. yvalve currently supports both APIs). ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
