Menu
▾
▴
firebird-devel
|
From: Mark O'D. <mar...@lu...> - 2001-09-20 23:27:33
|
Hi All Along with the discussions about the details of the next release and the Admin group has also been discussing the best methods of addressing the current Firebird compatibility issues for third-party tools and path for a longer term solution. Here are the decisions which we arrived at: 1 - For v1.0, the "version string" returned by the server will be fixed as "6.2.0.xxx". The engine and install packages will, however, carry the version number of "v1.0.0" 2 - The Windows install packages will be changed to ensure that they will overwrite any existing client libraries, regardless of version. Thus, ensuring that the latest Firebird client has been installed (instead of keeping the old IB 4.x/5.x/6.x version). And if possible the install will rename the existing dll rather than deleting it. 3 - The v1.0 Server/Client API will be extended to allow for tools to interogate the server to determine the engine flavor (Firebird vs. Interbase) and the 'real' Firebird version number (i.e. "1.0.0.xxx"). Full details of the API changes will be made available in the next couple of days. 4 - To address backward compatibility, the next major release of Firebird will listen on two ports: 3050 for InterBase(r) compatible clients, where the engine will provide an InterBase(r) compatible interface; and another port, yet to be decided upon, for new Firebird client connections. The new port will return "1.0.0" version strings, and allow the introduction of Firebird specific features (such as compressed over-the-wire protocol, more robust logon protocol, etc...) that would otherwise break backward compatibility. It is expected the name of the Firebird client shared object/dynamic link library will also change to a Firebird specific name at this time. The new Firebird client will allow connection to either the compatible 3050 port or the new FirebirdSQL server port. Thanks to all who participated in the discussion and helped resolve these issues. Posted on behalf of: The Firebird Admin Team (The FAT) by Mark. -- Your database needs YOU! http://www.firebirdSQL.org |
|
From: Danny M. <dma...@co...> - 2001-09-21 00:27:01
|
Mark,
Could I suggest that it may be a good idea to have FB listen on a new port
with every major version change. This would allow people to run multiple
versions of FB as they switch over from one version to another. This has
been a big problem in the past. Some other changes would also be needed on
the server and client but this is the most serious sticking point. What I
have in mind is that the 'services' file would contain entries like:
fb_db1 3051 #FB Version 1
fb_db2 3052 #FB Version 2
fb_db3 3053 #FB Version 3
:
Probably we could cycle the port numbers every 5 or 10 major versions. The
server and client installs should take care of updating the 'services' file
accordingly.
Regards,
Danny.
P.S. Do you think our overseas friends would understand the reference to
"The FAT"? :-)
"Mark O'Donohue" <mar...@lu...> wrote in message
news:3BA...@lu......
>
> Hi All
>
> Along with the discussions about the details of the next release and the
> Admin group has also been discussing the best methods of addressing the
> current Firebird compatibility issues for third-party tools and path for
> a longer term solution.
>
> Here are the decisions which we arrived at:
>
> 1 - For v1.0, the "version string" returned by the server will be fixed
> as "6.2.0.xxx". The engine and install packages will, however, carry the
> version number of "v1.0.0"
>
> 2 - The Windows install packages will be changed to ensure that they
> will overwrite any existing client libraries, regardless of version.
> Thus, ensuring that the latest Firebird client has been installed
> (instead of keeping the old IB 4.x/5.x/6.x version). And if possible the
> install will rename the existing dll rather than deleting it.
>
> 3 - The v1.0 Server/Client API will be extended to allow for tools to
> interogate the server to determine the engine flavor (Firebird vs.
> Interbase) and the 'real' Firebird version number (i.e. "1.0.0.xxx").
> Full details of the API changes will be made available in the next
> couple of days.
>
> 4 - To address backward compatibility, the next major release of
> Firebird will listen on two ports: 3050 for InterBase(r) compatible
> clients, where the engine will provide an InterBase(r) compatible
> interface; and another port, yet to be decided upon, for new Firebird
> client connections. The new port will return "1.0.0" version strings,
> and allow the introduction of Firebird specific features (such as
> compressed over-the-wire protocol, more robust logon protocol, etc...)
> that would otherwise break backward compatibility. It is expected the
> name of the Firebird client shared object/dynamic link library will also
> change to a Firebird specific name at this time. The new Firebird
> client will allow connection to either the compatible 3050 port or the
> new FirebirdSQL server port.
>
>
> Thanks to all who participated in the discussion and helped resolve
> these issues.
>
>
> Posted on behalf of:
>
> The Firebird Admin Team (The FAT)
>
> by Mark.
>
> --
> Your database needs YOU!
> http://www.firebirdSQL.org
>
>
>
> _______________________________________________
> Firebird-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
|
|
From: Martijn T. <m.t...@up...> - 2001-09-21 10:24:41
|
Hi Marc, > Here are the decisions which we arrived at: > > 1 - For v1.0, the "version string" returned by the server will be fixed > as "6.2.0.xxx". The engine and install packages will, however, carry the > version number of "v1.0.0" Will it hold 'Firebird' in the returned string '6.2.0.xxx' string? I'm using that now to determine Firebird specific features (beta 1.0.0.338 does this). -- Martijn Tonies Upscene Productions InterBase Workbench - The Developer Tool for InterBase http://www.interbaseworkbench.com |
|
From: Ann W. H. <aha...@ib...> - 2001-09-21 13:52:28
|
At 10:28 AM 9/21/2001 +1000, Danny Mavromatis wrote: >Could I suggest that it may be a good idea to have FB listen on a new port >with every major version change. This would allow people to run multiple >versions of FB as they switch over from one version to another. A much better solution is to get the Y-valve working correctly so it can direct calls to whichever engine is appropriate for the named database. Regards, Ann www.ibphoenix.com We have answers. |
|
From: David R. R. <ibi...@ma...> - 2001-09-21 14:19:03
|
> 1 - For v1.0, the "version string" returned by the server will be fixed > as "6.2.0.xxx". The engine and install packages will, however, carry the > version number of "v1.0.0" Will the file version resources contain 6.2.0.x or 1.x? They will need to be 6.2.0.x for the installer to know that the versions of the files that it is installing are 6.2.0.x. > 2 - The Windows install packages will be changed to ensure that they > will overwrite any existing client libraries, regardless of version. > Thus, ensuring that the latest Firebird client has been installed > (instead of keeping the old IB 4.x/5.x/6.x version). And if possible the > install will rename the existing dll rather than deleting it. What about interbase.msg? If we rename gds32.dll, shouldn't we also rename interbase.msg at the same time since the two files are basically married? BTW, the Wise scripts always create a backup folder and put any replaced files in that folder. There is also another option to change the installer so that if it finds a version of IB prior to 6.2.0.x, it will abort the installation and display a message that they previous version should be removed before continuing. Thoughts? -- David R. Robinson InterBase Installation Info - http://ibinstall.defined.net |
|
From: Danny M. <dma...@co...> - 2001-09-23 23:29:57
|
Ann, How would this work for SS? It listens on a particular port and then hands over a new connection to a thread. It is the listening on a particular port that is the issue (before it even gets to the Y-valve I think). Or are you talking about something at the client end? If so, then how does the client know what servers are available and how does it target them separately over TCP/IP? Surely the same issue arises, that you need a different port number for each server. Regards, Danny. ""Ann W. Harrison"" <aha...@ib...> wrote in message news:5.1...@fi...... > At 10:28 AM 9/21/2001 +1000, Danny Mavromatis wrote: > > >Could I suggest that it may be a good idea to have FB listen on a new port > >with every major version change. This would allow people to run multiple > >versions of FB as they switch over from one version to another. > > A much better solution is to get the Y-valve working correctly so it > can direct calls to whichever engine is appropriate for the named > database. > > > Regards, > > Ann > www.ibphoenix.com > We have answers. > > > > _______________________________________________ > Firebird-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-devel > |
|
From: Ann W. H. <aha...@ib...> - 2001-09-24 11:25:30
|
At 09:30 AM 9/24/2001 +1000, Danny Mavromatis wrote >How would this work for SS? It listens on a particular port and then hands >over a new connection to a thread. It is the listening on a particular port >that is the issue (before it even gets to the Y-valve I think). The thing that listens on the port accepts incoming communication and calls into the Y-valve for it to dispatch the call either to a local access method or on to another remote interface. There can be several local interfaces for different database types. Each tries to read the file and, if it fails, passes the request back to the Y-valve. Regards, Ann www.ibphoenix.com We have answers. |
|
From: Naoto G. <n-...@ji...> - 2001-11-01 09:45:49
|
Mark O'Donohue <mar...@lu...> さんが、2001/9/21 8:28:8に送られ た ---“Re-[Firebird-devel] Firebird version and Interbase/third-party tools compatibility for v1.0 and beyond”によりますと > > Hi All > > Along with the discussions about the details of the next release and the > Admin group has also been discussing the best methods of addressing the > current Firebird compatibility issues for third-party tools and path for > a longer term solution. > > Here are the decisions which we arrived at: > > 1 - For v1.0, the "version string" returned by the server will be fixed > as "6.2.0.xxx". The engine and install packages will, however, carry the > version number of "v1.0.0" > > 2 - The Windows install packages will be changed to ensure that they > will overwrite any existing client libraries, regardless of version. > Thus, ensuring that the latest Firebird client has been installed > (instead of keeping the old IB 4.x/5.x/6.x version). And if possible the > install will rename the existing dll rather than deleting it. > > 3 - The v1.0 Server/Client API will be extended to allow for tools to > interogate the server to determine the engine flavor (Firebird vs. > Interbase) and the 'real' Firebird version number (i.e. "1.0.0.xxx"). > Full details of the API changes will be made available in the next > couple of days. > > 4 - To address backward compatibility, the next major release of > Firebird will listen on two ports: 3050 for InterBase(r) compatible > clients, where the engine will provide an InterBase(r) compatible > interface; and another port, yet to be decided upon, for new Firebird > client connections. The new port will return "1.0.0" version strings, > and allow the introduction of Firebird specific features (such as > compressed over-the-wire protocol, more robust logon protocol, etc...) > that would otherwise break backward compatibility. It is expected the > name of the Firebird client shared object/dynamic link library will also > change to a Firebird specific name at this time. The new Firebird > client will allow connection to either the compatible 3050 port or the > new FirebirdSQL server port. > > > Thanks to all who participated in the discussion and helped resolve > these issues. > > > Posted on behalf of: > > The Firebird Admin Team (The FAT) > > by Mark. > > -- > Your database needs YOU! > http://www.firebirdSQL.org > > > > _______________________________________________ > Firebird-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-devel > > > ================================================ Naoto Gohko (郷古 直仁, システム開発部) <mailto:n-...@ji...> Jicoo Co. (株式会社 時空) <http://www.jicoo.co.jp/> ================================================ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X