<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
i admit to being somewhat addicted to C# scripting now so i'd second
the vote for LSL & C#.<br>
<br>
however, there is another question here... long term, how do you manage
interoperability between regions when the different simulators support
diverse scripting engines? the simple answer is "you don't"... the only
region an object should be expected to behave correctly is the one in
which it was created. that approach, however, seems somewhat...
unsatisfying (sarcasm intended) unless you are will to assert that all
simulators in a grid will provide the same capabilities. <br>
<br>
two other alternatives come to mind... <br>
<br>
first, there is a single standard "intermediate" representation which
all the various scripting engines translate into. this would have to
include a common set of APIs (eg the LSL and OS functions currently
supported). today, C# is that intermediate representation and, so long
as the C# is what's passed from region to region, it should work (that
does mean that the assets should store both the native script and the
translated c# or whatever the intermediate representation in order to
ensure portability).<br>
<br>
a second alternative is to negotiate script representations on region
crossing. the new simulator supports some languages/APIs, the object
requires some set of functions, and they negotiate a behavior. that
could get pretty ugly, but given that there is no way to control what
extensions one region provider will support, there will have to be some
capability negotiation (even if the outcome is as simple as "this
region can't support that object"). <br>
<br>
thoughts???<br>
<br>
--mic<br>
<br>
<br>
Kurt Taylor wrote:
<blockquote
cite="mid:OF5E01902C.F1273AB5-ON8625745C.0046B96D-8625745C.00475E05@us.ibm.com"
type="cite">
<p>Agreed, I'd vote to only ship LSL. Maybe C#. Everything else
optional. CPANish repository would be perfect.<br>
<br>
krtaylor - Kurt Taylor<br>
<br>
<br>
<tt><a class="moz-txt-link-abbreviated" href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a> wrote on 06/01/2008 10:45:48
PM:<br>
<br>
> I'm personally quite in favour of us developing a CPAN-like
repository<br>
> for OpenSim modules. To me it makes a very good deal of sense.<br>
> <br>
> Regards,<br>
> <br>
> Adam<br>
> <br>
> -----Original Message-----<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a><br>
> [<a moz-do-not-send="true"
href="mailto:opensim-dev-bounces@lists.berlios.de">mailto:opensim-dev-bounces@lists.berlios.de</a>]
On Behalf Of Justin<br>
> Clark-Casey<br>
> Sent: Sunday, 1 June 2008 8:44 PM<br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> Subject: [Opensim-dev] Should the core OpenSim distribution carry<br>
> manyscripting languages?<br>
> <br>
> Hi there,<br>
> <br>
> Last week, Kinoc was kind enough to write an implementation of
Yield <br>
> Prolog where YP is translated into underlying C# for compilation
(in the<br>
> <br>
> same manner as our current LSL support). This patch was included
in <br>
> OpenSim in r4927.<br>
> <br>
> I have nothing against Prolog (admittedly I have never had the
chance to<br>
> <br>
> pick up) and certainly nothing against Kinoc. However, I am
concerned <br>
> that by including many scripting languages in the OpenSim core <br>
> distribution (if Prolog, why not Javascript, Ruby, Python, etc,
etc.) we<br>
> <br>
> incur more negatives than positives. Firstly, I'm concerned that
a <br>
> proportion of this code (particularly that which no core committer
has <br>
> an interest in) will at some point slip into decay, particularly
if the <br>
> original contributor has moved on to other things. We've already
seen <br>
> this happen with other areas of the code, such as the MSSQL
database <br>
> support.<br>
> <br>
> Secondly, if individual language modules do need to change in
response <br>
> to other OpenSim changes without a decay option (for example, in
order <br>
> that they can still compile), this places a higher burden on the
core <br>
> committers and makes it more costly to enhance the codebase in
general.<br>
> <br>
> Thirdly, I'm concerned that the more code we have of this nature <br>
> (particular code which compiles script into c#), the more
potential <br>
> security holes we have. This isn't too much of a concern right
now but <br>
> will be come more of an issue in the future.<br>
> <br>
> Therefore, I would argue that OpenSimulator should only include in
its <br>
> core distribution support for a few scripting languages. In my
opinion <br>
> these would be LSL, maybe C# and possibly one other (maybe
Python). <br>
> Support for other languages would come as optional plugins,
available <br>
> either directly from the author or from some satellite repository <br>
> (perhaps similar to Perl's CPAN or PHP's PEAR). I would
personally <br>
> prefer to see the core OpenSim distribution kept relatively lean
and<br>
> mean.<br>
> <br>
> If necessary, I am happy to make any necessary infrastructure
changes to<br>
> <br>
> make language plugins possible/easier (which probably also means
making <br>
> much needed enhancements to the plugin system).<br>
> <br>
> What do other people think?<br>
> <br>
> Regards,<br>
> <br>
> -- <br>
> justincc<br>
> Justin Clark-Casey<br>
> <a moz-do-not-send="true" href="http://justincc.wordpress.com">http://justincc.wordpress.com</a><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a moz-do-not-send="true"
href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a moz-do-not-send="true"
href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</tt></p>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>