Perhaps if you told us which compilers and languages you were thinking of porting, or the kinds of problems that you anticipate solving, it would give us more information to go with?
There are networking classes built on top of async APIs that would be useful for wide area concurrency, for example, in addition to the SMP-centric constructs that Jason mentioned. -- David -----Original Message----- From: Jason Whittington [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 8:13 AM To: 'Angel Tsankov'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Dotnet-sscli] Asynchronous programming for Rotor You might get a better response if you forward the question to the Rotor list at discuss.develop.com, so I'm cross-posting over there. The support for asynchronous programming on the Rotor platform basically mirrors the support in .NET proper. I haven't written exhaustive tests but you will find support for asynchronous delegates and Monitor-based synchronization, which in the .NET world are the real core constructs. If you look through the System.Threading namespace you will find all the other usual synchronization primitives. There are a number of "intro to .NET" books available, any of which briefly cover the namespace. Did you have more particular questions? Jason > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:dotnet-sscli- > [EMAIL PROTECTED]] On Behalf Of Angel Tsankov > Sent: Monday, April 15, 2002 12:15 AM > To: [EMAIL PROTECTED] > Subject: [Dotnet-sscli] Asynchronous programming for Rotor > > Hi! I'm involved in a research team about asynchronous and > concurrent programming and we would like to port some > existing languages and compilers. So we would like what > rotor's support for cuncurrent and/or asynchronous > programming is. We would appreciate any information > including web sites, articles, books, drafts ... _______________________________________________ Dotnet-sscli mailing list [EMAIL PROTECTED] http://mailserver.di.unipi.it/mailman/listinfo/dotnet-sscli
