On Mon, 28 Aug 2000, Daniel Wickstrom wrote:

> >>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
> 
>     Mo> On Wed, 23 Aug 2000, Daniel Wickstrom wrote:
>     >> 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.
>     >> 
>     >> -Dan
> 
>     Mo> Just a quick update, I moved the cache into thread local
>     Mo> storage and reworked a bunch of stuff to support it. Things
>     Mo> should be fully thread safe now. If you want to take another
>     Mo> peek you are welcome to, of course you might have to wait
>     Mo> until monday morning for the CVS mirror to update.
> 
> 
> Ok thanks.  I'll take a look at it tonight.  
> 
> When do you anticipate finishing your work on the ajuba contract
> branch?

There is no clear date.

>  Also, when I get tclblend working in aolserver, would you be
> interested in incorporating the changes in tclblend as a conditional
> compile option to support aolserver?  I will try to minimize the
> changes to tclblend as much as possible.

What would you need to change? I can't agree to something
without knowing what it would entail.

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

Reply via email to