ly 18, 2000 11:19 AM
To: Jiang Wu
Cc: [EMAIL PROTECTED]
Subject: RE: [Tcl Java] tclBlend / tcl thread workaround
Jiang,
thanks for the response
You can do:
Tcl Thread
A -> package require java -> start JVM ...
Tcl Thread
B -> send request to Tcl thread A for Java work
esday, July 18, 2000 1:21 PM
> To: [EMAIL PROTECTED]
> Subject: [Tcl Java] Re: [Tcl Java] RE: [Tcl Java] tclBlend /
> tcl thread
> workaround
>
>
> ... A post written in HTML ...
>
The TclJava mailing list is
... A post written in HTML ...
Please do not post to the tcljava list in HTML. People
will text email clients can not read what you are posting!
Mo DeJong
Red Hat Inc
The TclJava mailing list is sponsored by Scriptics Corporation.
You
are correct that the code can block if Tcl thread A blocks on doing some
work. To share a single thread amount multiple threads, the single thread
can provide non-blocking operations. For example:
Tcl
Thread A:
loop waiting for request from
other Tcl threads {
*
accep
Jiang,
thanks for the response
You can do:
Tcl Thread
A -> package require java -> start JVM ...
Tcl Thread
B -> send request to Tcl thread A for Java work using
message passing on the event queue of A
Tcl Thread
C -> send request to Tcl thread A for Java work ...
IL PROTECTED]
> -Original Message-
> From: Mike Schwartz [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 17, 2000 9:22 PM
> To: Mo DeJong; [EMAIL PROTECTED]
> Subject: [Tcl Java] tclBlend / tcl thread workaround
>
>
> so, I just had another idea:
>
> I don't
so, I just had another idea:
I don't really need (or even want) more than 1 JVM for all the tcl threads.
On the Java side I have threads that allow concurrency among incoming
requests, so the structure I really want is:
- master tcl thread does 'package require java', which creates an in
