> Hello, > > Mathias Hasselmann wrote... > >>I'm also voting for the mono based service manager. Additionally to the > >>compatibility issue I could imagine that we also would gain some > >>efficience from using a mono based service manager: See the Mono runtime > >>would be launched only once (potentially faster startup) and as long as > >>not explicitly requested to deal it different all the services could > >>life in appdomains of the same mono vm... > > putting all services in one SysV process is a bad idea. Because, if one > hangs or crashed the hole mono::SCM is crushing. Appdomains are not the solut > ion. > For example if a p/invoke process crushed the appdomain has no change to > recover this process.
I'm not really involved in this discussion, but to me, this solution of having a mono-based service manager sounds a lot like creating a mono version of init for mono-based processes. -- Tim Coleman <[EMAIL PROTECTED]> [43.43 N 80.45 W] BMath, Honours Combinatorics and Optimization, University of Waterloo Software Developer, Global Services, Open Text Corporation "Under capitalism, man exploits man. Under communism, it's just the opposite." -- J.K. Galbraith _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
