On Fri, Nov 30, 2007 at 04:43:03PM +0100, Gevik Babakhani wrote:
> > I did look at this at some earlier point as well. One big
> > problem at that time was that once you embedded mono, you had
> > all sorts of threads running in your backend ;-)
>
> yes, threads running around could become a show stopper for both Mono and
> MS.NET
> This is something I want to be sure of before I begin.
Yaeh.
> > Another way to do it is "the PL/J" way (I think). Which is
> > starting up a separate process with the VM in it and then do
> > RPC of some kind to it.
> > Which has more overhead per call, but lower per backend etc.
> > And a lot less "dangerous".
>
> This is actually my plan B, hence it is less dangerous.
> I am thinking the "started process" can stay alive and act
> as a service of some kind to handle/answer calls form multiple
> backends and shutdown itself after a period of time being
> idle.
Yes, you should have just one such process with .Net managed threads
running inside it. You just need to find a good RPC library to pass things
back and forth between the backend running natively and this special
process running in .net.
//Magnus
