Subject | RE: [firebird-support] Re: Optimising High Latency Database Connections |
---|---|
Author | Louis van Alphen |
Post date | 2015-01-21T14:40:28Z |
OK then I stand corrected. But I still prefer a services layer approach
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: 21 January 2015 03:09 PM
To: 'Louis van Alphen' louis@... [firebird-support]
Subject: Re: [firebird-support] Re: Optimising High Latency Database Connections
LvAlnczfs> Personally I won’t connect directly over a high latency
LvAlnczfs> connection. You risk inconsistent updates and corruption.
You are wrong. You cannot corrupted database because you are using a
connection over a high latency network. The same applies for
inconsistent updates (that's why transaction control exists).
Btw, FB 3 has a much better protocol performance in such networks, as
seem in my published test results:
http://www.firebirdnews.org/testing-the-firebird-3-protocol-enhancements/
[]s
Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org - www.FireBase.com.br
[Non-text portions of this message have been removed]
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: 21 January 2015 03:09 PM
To: 'Louis van Alphen' louis@... [firebird-support]
Subject: Re: [firebird-support] Re: Optimising High Latency Database Connections
LvAlnczfs> Personally I won’t connect directly over a high latency
LvAlnczfs> connection. You risk inconsistent updates and corruption.
You are wrong. You cannot corrupted database because you are using a
connection over a high latency network. The same applies for
inconsistent updates (that's why transaction control exists).
Btw, FB 3 has a much better protocol performance in such networks, as
seem in my published test results:
http://www.firebirdnews.org/testing-the-firebird-3-protocol-enhancements/
[]s
Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org - www.FireBase.com.br
[Non-text portions of this message have been removed]