[Mono-devel-list] Embedding Mono in a Virtual World
kellyleahy at swbell.net
Fri Mar 18 16:25:25 EST 2005
I don't see how this could possibly work if the
managed code objects you are trying to persist deal in
any way with resources outside of the managed world.
For instance, I assume threads are implemented as
either some pthreads based objects or some windows
threads objects (in the kernel sense of the word
object, of course) and you cannot possibly expect
anything running in the managed world to know how to
"persist" these things unless the managed objects
specifically know how to do this (i.e. are designed to
support this functionality).
Or am I missing the point?
--- Jim Purbrick <jimpurbrick at yahoo.co.uk> wrote:
> --- "Rodrigo B. de Oliveira"
> <rodrigobamboo at gmail.com>
> > You might be able to cook up something with
> > serializable objects and lightweight threads based
> > on generators (yield).... But this is just
> > food for though...
> Yes, this is the other option. You end up with
> something that looks like PicoThreads for Java, or
> some of the other Java systems for serializing
> threads. It boils down to builing continuations on
> heap instead of using the stack. As the continuation
> objects are just objects you can serialize them like
> any other object. Then you just need to turn every
> method in to a state machine so you can jump to any
> point in the method. This is lots of work though and
> has a big impact on performance, so I'm hoping I
> have to go there. Trying to use debugging APIs to do
> this sounds like it might be an easier first option.
> Send instant messages to your online friends
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list