On Wed, 23 Aug 2000, Daniel Wickstrom wrote:
> After moving back to the u.s., I've started looking into integrating
> tclblend into aolserver/nsjava again. Last night I checked out the cvs
> sources from the cvs ajuba contract branch, and started to compare it
> to version 1.2.6.
Welcome back. The taxes are high, the crime rates are low,
at almost 5% of the population is in jail. You gotta love the US.
> I'm curious about the JavaInfo structure in javaCmd.c. When I looked
> at this before, I assumed that you would need a seperate JavaInfo
> structure per thread. The code I'm looking at now seems to assume one
> global JavaInfo structure that can be used by all tcl threads. Am I
> missing something here, or is this part of the code still work in
> progress? I thought I read somewhere in the java docs that class and
> method ids can't be shared between java threads.
I took another look at the docs and found this note:
http://java.sun.com/products/jdk/1.1/docs/guide/jni/spec/functions.doc.html#16027
"Note that the function table can be shared among all JNI interface
pointers."
So it looks like you are right, we need to put the method cache
in thread local storage. The contract branch is clearly not
finished, there is a lot of work that still needs to be done.
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
