It seems to me that most people still talk about untrusted,
portable, and grid-wide supported downloadable scripts when
talking about Client-side scripting (sorry Morgaine).
So, I propose to go with that, and call anything else
The remainder of this post is about Client-extensions.
I sense consensus on the following layered design:
[current code base]
+ lots of hooks to be written
C++ API 
IPC API 
One or more plugins then could provide a client-side
- A scripting engine for language XYZ.
 Ie, based on the yet to be written LLStateMachine class.
PS Note that personally I'm against using mono for
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.