New implementation for wire protocol in Jaybird and all drivers need a faster wire protocol
Mark Rotteveel wrote on twitter about the Jaybird improvement:
Writing a new implementation of the wire protocol in Jaybird. I fear it is going to cascade into a total rewrite of the driver
Jiri chatted later:
IMO the whole “communication layer” needs redesign. It’s (way) too legacy.
And later on the twitter channel Brent Rowland wrote:
Contemplating creating a new wire protocol. Stop me now…
I have a replication system for Firebird I need to extend across a WAN. Firebird has no built-in replication and the protocol is chatty.
Editor:All these conversations are around Firebird 2.5.x protocol , there is work conducted by Dmitry Yemanov on improving the Firebird 3.x protocol
Loading...
Last year, FDD collected money to sponsor FB protocol enhancements. The task should be done by Dmitry Yemanov, but it seems that he is still busy with other tasks and didn’t make progress on this subject yet 🙁
PS: Enhancement of the wire protocol is the top voted feature in the tracker.
I know he is busy , maybe it would be great if we can discuss about the protocol enhancements on the list or at least it would be great some new blogs from core devels
I think Dmitry will update his blog as soon he finds time to play with the subject again.
Looking forward, I have a replication engine and I have troubles maintaining DB’s in synch, specially when connections are off for days. I’m working on a separate communication layer based on remote objects libraries.