There's an interesting side-question that's worth considering.... And that's whether an application that calls lots of short JNI methods on an extremely frequent basis suffers at all. It *MIGHT* affect the style of programming.
I know of one case where the customer would be doing joins in the java code - rather inside DB2 (in the JDBC / SQLJ case). Somehow I would think that almost provably pessimal. :-) Anyone done any thinking on JNI and efficiency/effectiveness? NOTE: I don't work for the Washington Systems Center so, while an IBMer, I'm not teasing to hit anyone with an official line. Just thinking aloud. If you can call it thinking. :-) Hopefully this ISN'T too far off topic. Thanks, Martin Martin Packer Performance Consultant IBM United Kingdom Ltd +44-20-8832-5167 +44-7802-245-584 [EMAIL PROTECTED] Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
