|
To further refine the idea, user code can
be compiled from LSL to C#, and then accessed by the main server code through
.Net Remoting. When the code is on the same machine, there is negligible overhead.
This is especially true when compared to actually implementing a VM on
top of the .Net CLR. -Samuel Vincent From: Vincent, Samuel Ah, that actually makes more sense.
Emitting your own CIL opens up a world of possibilities for security
risk, as well as bugs. However, my suggestion would be to make LSL
compile to C#, possibly hidden from the users, and have a carefully designed
set of C# classes that implements LSL’s functionality behind the scenes.
This would give you the full performance of a C# application, the benefit
of a rich feature set available in .Net, and the security of being able to carefully
control the subset of .Net that is exposed to users. -Samuel Vincent From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Wilson I think what he's saying that the virtual machine that runs LSL run
inside of the .Net CLR... if that IS what he's saying, it's unnecessary,
since LL has already implemented an LSL compiler for Mono. For some reason,
though, they've just never transferred it to the rest of the grid (it's only
running on On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Perhaps I am misunderstanding what you just said. Are
you actually suggesting running the .Net CLR (.Net's virtual machine) on
top of a Java VM, thus giving us two nested virtual machines on top of the
native OS? -Samuel Vincent From: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] On
Behalf Of Jonathan One thing to note, I didn't mention my perspective
that would help explain my interest. A CLS, like Mono, usually implements
a runtime environment directly on top of a native environment. Given that CIL
is well defined, this direct implementation is not needed and can be divided
again with a VM, so that the CIL executable is within a runtime environment
directly on top of a VM instead of a native environment. This allows machine
states to be stored, retrieved, distributed, and networked across like or
different native environments. Current implementations of CLS (Mono and
Microsoft alike) are limited in their microthread abilities due to native
entanglements. The VM will solve that. It is expected this division will affect
performance, where many CLS implementers have touted native speed, at the trade
of such native speed in exchange for scalability and security. Java to CIL + C# to CIL = common sense
_______________________________________________libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/ --
_______________________________________________libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/ --
|
_______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/
