Re: Solaris Native thread problem

[Ted Neward]

Title: RE: Solaris Native thread problem

While I agree with you that there is a difference between the two, most threaded code that stays within the JVM can safely ignore the difference.   And anyone who relies upon Threads doing *anything* in a predictable order is bound to get into trouble, no matter what part of threading we're talking about. :)   Ted Neward Patterns/C++/Java/CORBA/EJB/COM-DCOM spoken here http://www.javageeks.com/~tneward  "I don't even speak for myself; my wife won't let me." --Me -----Original Message----- From: Andy Bailey <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thursday, July 22, 1999 7:52 PM Subject: Re: Solaris Native thread problem > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] >... > In a Java app that does not contain any JNI calls, there > should be *no* > changes required in the app code itself to switch between > native threads > and green threads (or any other undelrying thread model, for that > matter).  It is up to the JVM to provide an environment that supports > the thread semantics required by the Java API.  As long as But the semantics aren't fully defined.  For example, preemptive and non-preemptive JVMs exist.  While there are easy ways to ensure that your code behaves properly with both, you can't always ignore the difference. >... > Craig McClanahan Problems may occur when you are relying on Threads waking up and going to sleep in a predictable order Andy Bailey