26.09.2014 13:27, marius adrian popa :
I have seen this patch for openjdk
http://mail.openjdk.java.net/pipermail/net-dev/2014-September/008685.html
Maybe is worth to be implemented in Firebird also
Maybe is worth to be implemented in Firebird also
http://blogs.technet.com/b/wincat/archive/2012/12/05/fast-tcp-loopback-
performance-and-low-latency-with-windows-server-2012-tcp-loopback-fast-
path.aspx
Add to tracker, please.
Case 4563 created to implement Fast Path
Sean
I have seen this patch for openjdk
http://mail.openjdk.java.net/pipermail/net-dev/2014-September/008685.html
Maybe is worth to be implemented in Firebird also
Marius,
Maybe is worth to be implemented in Firebird also
http://blogs.technet.com/b/wincat/archive/2012/12/05/fast-tcp-loopback-
performance-and-low-latency-with-windows-server-2012-tcp-loopback-fast-
path.aspx
Localhost is not necessary for Classic and SuperClassic engine (I not sure of
26.09.2014 19:13, Leyne, Sean wrote:
Localhost is not necessary for Classic and SuperClassic engine (I not sure of
SuperServer, we don't use this mode), since local mode connections are
supported
XNET is not an option for Jaybird or .NET users.
since the long-term path for Firebird is the
XNET is not an option for Jaybird or .NET users.
Wasn't aware of that.
since the long-term path for Firebird is the deprecation of
SuperServer
You're surely misinformed.
If v3 has the SMP improvements which are planned, why would we continue to
support 3 engine versions?
Classic and
26.09.2014 20:11, Leyne, Sean wrote:
If v3 has the SMP improvements which are planned, why would we continue to
support 3 engine versions?
Classic and SuperClassic would have functionality which covers all use cases.
v3 has the SMP improvements in *SuperServer*.
Dmitry
On 26-9-2014 18:11, Leyne, Sean wrote:
XNET is not an option for Jaybird or .NET users.
Wasn't aware of that.
Well, actually it is possible with Jaybird (and probably with the .NET
provider as well), but most Java developers prefer not to use native
library dependencies.
since the
If v3 has the SMP improvements which are planned, why would we
continue to support 3 engine versions?
Classic and SuperClassic would have functionality which covers all use
cases.
v3 has the SMP improvements in *SuperServer*.
Ok
FYI, the 2.5.x release notes suggest that
