>But what about "true" multitasking? In my experience, green threads
>don't do that very well.
In Java, green threads may not do multitasking at all. Java makes no
guarantees about preemptive threading - it's entirely correct for one
thread to dominate the CPU, as long as it's the highest priority.
Java makes very few guarantees at all about thread execution. If I
understand the spec right, it's even correct for Thread.yield() to do
nothing at all, although that would be pathological.
So it's good to use native threads, because you get preemptive
multitasking, but code that relies on that is non-portable.
[EMAIL PROTECTED]
. . . . . . . . http://www.media.mit.edu/~nelson/
- Another JDK 1.2 Status Report Kevin B. Hendricks
- RE: Another JDK 1.2 Status Report Kontorotsui
- Re: Another JDK 1.2 Status Report peter . pilgrim
- JavaSound and JMF performance [was Re: ... Alexander V. Konstantinou
- Re: JavaSound and JMF performance [... peter . pilgrim
- RE: Another JDK 1.2 Status Report Christian Seiler
- Native threads in Java Nelson Minar
- Re: Another JDK 1.2 Status Report Juergen Kreileder
- RE: Another JDK 1.2 Status Report Peter Schuller
- Green/Native threads Nelson Minar
- Green/Native threads Gerald Gutierrez
- Re: Green/Native threads Dimitris Vyzovitis
- Re: Green/Native threads Juergen Kreileder
- Re: Green/Native threads David Craig
