Best practice for time-critical and reliable JNI calls
0 posts in topic
Flat View  Flat View

Posted By:   Anonymous
Posted On:   Tuesday, May 3, 2005 12:01 PM

After reading "Traps & Pitfalls" chapter from Sheng Liang book, I concluded with the rule that try to write JNI call stateless and simple.

For the sake of simplicity and the performance I merged different native call into one native call. But this will leads to the increase in argument list of that new native call (25 variables).

Now advice me, Is this approach is correct or any other best way to reduce argument list of a native call? (Note: This native call is time-critical so it must be fast and reliable).

And also, how I will send unsigned 32 bits (integer) from java to c?

About | Sitemap | Contact