[Opensim-dev] Thoughts on Scripting

[J Ross Nicoll]

I like the idea of having the script explicitly manage its own state,  
but this either means a massive divergence from how Second Life  
handles state, or getting a lot of changes past the Lindens. https://jira.secondlife.com/browse/SVC-966 
  ("Script configuration object type") would be a good start for  
having SL-native scripts be able to store state in any useful way, at  
least.

On 14 Sep 2008, at 06:07, Mike Deem wrote:

> Perhaps scripts should be responsible for explicitly storing and  
> fetching state as needed. That is how the vast majority of  
> programming environments work. There is usually no expectation that  
> a running program's state is preserved at all times.
>
> A simple get/put property bag API could be provided by the platform.  
> Such an API could be backed by a local DB, an assert server, or even  
> a cloud store like Amazon S3 or something.
>
> External script servers may also make load balancing easier. A  
> single srever could handle scripts in multiple regions, or a single  
> reagion's scripts could be spread across multiple script servers.  
> Also, moving all script HTTP, e-mail, and RPC I/O to a different  
> machine could help balance network load.
>
>   == Mike ==
>
>
> On Sat, Sep 13, 2008 at 9:30 PM, Dahlia Trimble <dahliatrimble at gmail.com 
> > wrote:
> I'm not sure I agree, periodic state backups could preserve quite a  
> bit of information, and machines hosting simulators can fail just as  
> a machine hosting a script server. Not sure I agree with the delays  
> either as the script server may even be able to do things faster  
> since it may only have script processing to do and doesn't have to  
> spend time processing physics or whatnot. If it was able to  
> communicate all the changes that needed to happen in a server frame  
> before the next frame starts then it may actually be a faster  
> design. I guess a lot depends on how it's implemented.
>
>
> On Sat, Sep 13, 2008 at 4:32 AM, J Ross Nicoll <jrn2005 at cs.st-andrews.ac.uk 
> > wrote:
> The problem with an external script server is you're still doomed if
> the server goes down. You need to be able to serialise state anyway or
> the first extended powercut/hardware fault/intern looking for a kettle
> lead will cause unspeakable chaos.
>
> You'd also be bringing in even more delay in script response time, but
> that's relatively minor.
>
> On 7 Sep 2008, at 15:52, Mike Deem wrote:
>
> > I've also been thinking about things like global scripts and
> > external script servers. External script servers would solve some of
> > the script state serialization issues. Instead of moving a running
> > script from one region to another, it just keeps running on it's
> > server.
>
> The University of St Andrews is a charity registered in Scotland : No
> SC013532
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev

The University of St Andrews is a charity registered in Scotland : No  
SC013532



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080916/64fd2a61/attachment-0001.html>