On 26-9-2014 18:11, Leyne, Sean wrote: >> XNET is not an option for Jaybird or .NET users. > > Wasn't aware of that.
Well, actually it is possible with Jaybird (and probably with the .NET provider as well), but most Java developers prefer not to use native library dependencies. >>> since the long-term path for Firebird is the deprecation of >>> SuperServer >> >> You're surely misinformed. > > If v3 has the SMP improvements which are planned, why would we continue to > support 3 engine versions? > > Classic and SuperClassic would have functionality which covers all use cases. It doesn't: SuperServer has shared cache, which neither Classic and SuperClassic have. However Firebird 3 has a unified executable: it is now a configuration option, not a different executable. Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
