I'm certainly in favor of such configurability early on. I'm sure I needn't
bring up the recent scheduler drama in the Linux world. As long as the calls
are optimized enough so as to not add crazy overhead to such a critical
piece of code.
And most definitely appdomains are the process equivalent. As I've always
seen it there are shared assemblies, system appdomains, and user appdomains.
Perhaps only one giant system appdomain.
Food for thought: JX's kernel scheduler only prioritizes appdomains - thread
scheduling is configurable on a per appdomain basis.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
