[Firebird-devel] Wire protocol changes in Firebird 4?
Are there any wire protocol changes in Firebird 4 (or planned for Firebird 4). And if so, where can I find information on those changes? Mark -- Mark Rotteveel -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
19.12.2016 19:51, Mark Rotteveel wrote: > Are there any wire protocol changes in Firebird 4 (or planned for > Firebird 4). And if so, where can I find information on those changes? I could remember the only small change, bug fix for CORE-5296 by Alex (commit 056164ab95c0ae52c970ab6603cf54d18fbc152f). I plan to introduce little change to pass statement timeout (op_execute, op_execute2). Details will be published soon. Regards, Vlad -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
No improvements regarding blob transfer? Even with the enhancements in 3.0, transferring blobs is still slow compared to other datatypes. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br VK> 19.12.2016 19:51, Mark Rotteveel wrote: >> Are there any wire protocol changes in Firebird 4 (or planned for >> Firebird 4). And if so, where can I find information on those changes? VK>I could remember the only small change, bug fix for CORE-5296 by Alex VK> (commit 056164ab95c0ae52c970ab6603cf54d18fbc152f). VK>I plan to introduce little change to pass statement timeout (op_execute, VK> op_execute2). Details will be published soon. VK> Regards, VK> Vlad VK> -- VK> Developer Access Program for Intel Xeon Phi Processors VK> Access to Intel Xeon Phi processor-based developer platforms. VK> With one year of Intel Parallel Studio XE. VK> Training and support from Colfax. VK> Order your platform today.http://sdm.link/intel VK> Firebird-Devel mailing list, web interface at VK> https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
20.12.2016 02:01, Carlos H. Cantu wrote: > > No improvements regarding blob transfer? No (yet). Dmitry -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
>From my point of view, protocol must be rewrited At minimum: 1. The each packet should contain the field with own size. 2. It is necessary to solve the problems with LazySend mode. Dmity Kovalenko www.ibprovider.com -Original Message- From: Mark Rotteveel [mailto:m...@lawinegevaar.nl] Sent: Monday, December 19, 2016 8:51 PM To: For discussion among Firebird Developers Subject: [Firebird-devel] Wire protocol changes in Firebird 4? Are there any wire protocol changes in Firebird 4 (or planned for Firebird 4). And if so, where can I find information on those changes? Mark -- Mark Rotteveel -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 12:10, Kovalenko Dmitry wrote: >>From my point of view, protocol must be rewrited > > At minimum: > 1. The each packet should contain the field with own size. > 2. It is necessary to solve the problems with LazySend mode. 1) Core team have no time for it. 2) Core team have no time to review big patches from outsiders. 3) Backward compatibility has to be kept. -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 14:19, Dimitry Sibiryakov wrote: > > 1) Core team have no time for it. True. > 2) Core team have no time to review big patches from outsiders. Bullshit. > 3) Backward compatibility has to be kept. True. What a surprise! Dmitry -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 12:19, Dimitry Sibiryakov wrote: > 1) Core team have no time for it. > 2) Core team have no time to review big patches from outsiders. > 3) Backward compatibility has to be kept. 4) Knowledge of total length of packet is required only for current parser which need full packet to be in single buffer. If rewrite parser to use stateful automate, total length is needless. -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
>4) Knowledge of total length of packet is required only for current parser which need full packet to be in single buffer. If rewrite parser to use stateful automate, total length is needless. No. It need for resolve a problem with cancelation of operations. http://tracker.firebirdsql.org/browse/CORE-5152 Dmitry Kovalenko -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Wire protocol changes in Firebird 4?
30.12.2016 15:52, Kovalenko Dmitry wrote: > No. It need for resolve a problem with cancelation of operations. > > http://tracker.firebirdsql.org/browse/CORE-5152 I'm sorry, but could you explain a little: how packet length can help in this case? > It will allow with minimal efforts detect the "op_cancel" operation in stream > of data packets at "SRVR_multi_thread" level. Does it mean that op_cancel packet can be send in the middle of any other packet? -- WBR, SD. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
