Re: JDK & native threads

1998-09-24 Thread Juergen Kreileder
> Gerald Gutierrez writes: >> If you check the Java-Linux bug database (jitterbug) you will see >> that I was the one to report this and that Kevin was the one who >> did most of the work to address this. > Jitterbug ? Is that the "Bug Reporting" page on Blackdown ? Not exaclty, JitterBug (

Re: JDK & native threads

1998-09-24 Thread Gerald Gutierrez
> If you check the Java-Linux bug database (jitterbug) you will see > that I was the one to report this and that Kevin was the one who > did most of the work to address this. Jitterbug ? Is that the "Bug Reporting" page on Blackdown ?

Re: JDK & native threads

1998-09-23 Thread Peter C. Mehlitz
>>> An alternative is Kaffe, but it's too incomplete to be usable right now. >>> Is anyone working on producing a version of the JDK that uses native >>> threads ? > >I don't know if Kaffe actually uses native threads... Since Native >Threads do not exist on FreeBSD, it for sure does not use them

Re: JDK & native threads

1998-09-23 Thread Michael Sinz
On Wed, 23 Sep 1998 09:42:48 -0700, Gerald Gutierrez wrote: >> (Ok, so on older versions, reads from STDIN/STDOUT/STDERR were a problem >> but this has been addressed) >> > > >Are you sure ? The following seems to indicate that at least >STDIN will block everything. Yes, I am sure - you need to

Re: JDK & native threads

1998-09-23 Thread Michael Sinz
On Wed, 23 Sep 1998 09:29:19 -0400 (EDT), [EMAIL PROTECTED] wrote: > >On Tue, 22 Sep 1998, Gerald Gutierrez wrote: > >> I'm starting to pull out my hair from the fact that the current JDK is >> based on user threads. I can't call anything that can potentially block, >> because everything will blo

Re: JDK & native threads

1998-09-23 Thread Gerald Gutierrez
> (Ok, so on older versions, reads from STDIN/STDOUT/STDERR were a problem > but this has been addressed) > Are you sure ? The following seems to indicate that at least STDIN will block everything. import java.io.*; public class Threads extends Thread { public static void main (String[]

Re: JDK & native threads

1998-09-23 Thread mab
On Wed, 23 Sep 1998, Alexander V. Konstantinou wrote: > [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote on Wed, Sep 23, 1998 at 09:29:19AM - > 0400: > > Are you saying that if my application has 5 threads running, and > > one of them blocks on a blocking method (i.e., BufferedReader.readLine() > >

Re: JDK & native threads

1998-09-23 Thread Alexander V. Konstantinou
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote on Wed, Sep 23, 1998 at 09:29:19AM - 0400: > Are you saying that if my application has 5 threads running, and > one of them blocks on a blocking method (i.e., BufferedReader.readLine() > on a client socket) then the 4 other threads are blocking (not run

Re: JDK & native threads

1998-09-23 Thread mab
On Tue, 22 Sep 1998, Gerald Gutierrez wrote: > I'm starting to pull out my hair from the fact that the current JDK is > based on user threads. I can't call anything that can potentially block, > because everything will block. > Are you saying that if my application has 5 threads running, and o

Re: JDK & native threads

1998-09-23 Thread Michael Sinz
On 23 Sep 1998 00:31:35 -0700, Anand Palaniswamy wrote: >> An alternative is Kaffe, but it's too incomplete to be usable right now. >> Is anyone working on producing a version of the JDK that uses native >> threads ? I don't know if Kaffe actually uses native threads... Since Native Threads do

Re: JDK & native threads

1998-09-23 Thread Anand Palaniswamy
Gerald Gutierrez <[EMAIL PROTECTED]> writes: > I'm starting to pull out my hair from the fact that the current JDK is > based on user threads. I can't call anything that can potentially block, > because everything will block. "Green threads" converts all your blocking I/O into non-blocking ones