You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For performance reasons, a Proxy will never be as fast as an actual delegate class. While the Proxy allows the library to be compatible with future Java versions that keep on adding methods to the Connection class hierarchy (as we got used to it by now), the performance penalty might be to much for paying of.
The ConnectionDecorator simply delegates all calls to the actual Connection object. The newer Java 1.7 and 1.8 methods are invoked using reflection, to allow compiling the project with Java 1.6
The text was updated successfully, but these errors were encountered:
vladmihalcea
changed the title
Add a new ProxyFactory to use a ManagedConnection delegate
Add a new ProxyFactory to use a ConnectionDelegate object instead of a Proxy
Jul 4, 2015
… of a Proxy
Add the new flexy-pool-core-java7 module to include all Java 1.7 JDBC additions
The ConnectionDelegate abstraction is using the same Service resolving mechanims like the MetricsFactory
…d of a Proxy
Activate Java 7 Connection Decorator resolver for Java 8 tests
vladmihalcea
changed the title
Add a new ProxyFactory to use a ConnectionDelegate object instead of a Proxy
Add a new ProxyFactory to use a ConnectionDecorator object instead of a Proxy
Jul 5, 2015
For performance reasons, a Proxy will never be as fast as an actual delegate class. While the Proxy allows the library to be compatible with future Java versions that keep on adding methods to the Connection class hierarchy (as we got used to it by now), the performance penalty might be to much for paying of.
The ConnectionDecorator simply delegates all calls to the actual Connection object. The newer Java 1.7 and 1.8 methods are invoked using reflection, to allow compiling the project with Java 1.6
The text was updated successfully, but these errors were encountered: