On Wed, Jun 03, 2015 at 11:08:36PM +0200, Michael Stahl wrote:
hmm... how about we solve the JDBC performance problem by, the first
time a Java component is created, the component-factory stuff posts
a message to the main thread via PostUserEvent with a handler that
does a "dummy" JNI call into some Java function that calls back via
JNI into another function that calls Application::Yield again; now
JNI calls will never *enter* the JVM on the main thread because it's
always *in* the JVM already - just needs cleaning up on quit, what
could possibly go wrong...
That kind of idea is intellectually interesting to me (something like
that was in the laundry list in
https://bugs.documentfoundation.org/show_bug.cgi?id=57872#c0 ), but I
don't think I can implement it :)
--
Lionel
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.