Green threads in Java go back to when they originally built the platform - they had to roll their own threads because they weren't running on top of an OS.
I don't know that such 'virtual' threads would have any advantage over native threads (if threads are available on the target platform) other than avoiding a context switch. I'm sure the disadvantages are many (isn't this why Java's IO was so crap until recently?) Jim > -----Original Message----- > From: Kevin Burton [mailto:[EMAIL PROTECTED]] > Sent: 19 April 2002 15:39 > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Green thread support > > > It sounds like Green Threads are equivalent to fibers. And I > am not aware of > any support other than through P/Invoke in .NET. Am I missing > the point? > > Kevin Burton > .NET Common Language Runtime Unleashed > > -----Original Message----- > From: Gavan Hood [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 19, 2002 8:29 AM > To: [EMAIL PROTECTED] > Subject: [DOTNET] Green thread support > > I have been advised today that DOTNET has support for what > Java guys refer > to as Green Threads, threads that are managed by the > application not by the > os. No context switching.... do a search on google if you > want the full > explanation. > Anyhow I do not know of any such support and cannot see > anything suggesting > this sort of support in dotnet... Does anyone know of any > such support. I > do not see this being thread pooling, managed threads to my > knowledge as > they are os related in the current version at least. > > Regards > Gavan > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
