On 01/04/12 13:46, Mark Rotteveel wrote: > On 4-1-2012 8:30, marius adrian popa wrote: >> On Wed, Jan 4, 2012 at 2:23 AM, W O<sistemas2000profesio...@gmail.com> >> wrote: >>> I agree. >>> >>> I just use FB 2.5 >>> >>> Greetings. >>> >>> Walter. >> I would go to accept only protocol from> 2.0 >> 1.5.x is not supported anymore anyway >> http://www.firebirdsql.org/en/roadmap/ > If you look at Jaybird it currently only supports protocol version 10, > and as long as the newer protocol versions are not implemented, removing > support for protocol version 10 would cut off all Java users from > connecting to Firebird 3.0 (except when using a native client library, > but that has its own downsides). > > I am planning on adding the newer protocol versions in Jaybird 2.3, but > it will take time to get familiar with the wire protocol and its current > implementation in Jaybird. What I have seen right now will probably mean > that I will need to rewrite the implementation to better/easier > accommodate multiple protocol versions. Then it will take more time to > test the new implementation and to have users migrate to Jaybird 2.3.
I think that support of protocol 13 should better be added to all clients due to one more reason - to use lower protocol versions one need to turn on legacy authentication on server, and this is security issue. What about keeping support for protocol 10 - one more reason to have it alive as long as possible. This is the last common between firebird and interbase protocol version. When I checked it on interbase server some time ago protocol 10 was supported. Ability to talk to interbase server using our client is important enough to keep that version support - at least as long as Embarcadero keeps it. Or even a few versions longer - there are will remain a bunch of servers to talk to using that protocol. > It would probably - correct me if I am wrong - also mean that EXECUTE > STATEMENT ON EXTERNAL feature of Firebird 3.0 cannot connect to some of > the earlier Firebird versions. If 2 firebirds have no common protocol - they can't talk. And it's absolutely no difference is it needed for EXECUTE STATEMENT ON EXTERNAL or for something else. ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
