Subj : Implementation Questions To : From : mike@electrotank.com (Michael Grundvig) Date : Fri May 09 2003 02:57 pm Hi all! First off, I want to thank everyone who has worked on Rhino, it's great! We have been able to use it with great success. The purpose of this email is to ask about how to implement Rhino effectivly. We have a server that supports the concept of plugins. A plugin is registered by a user and it contains a name, script on the file system and some initilization parameters. An object called ScriptPlugin is used for all this. When the server is restarted, it will load in all the plugins and init them. Then calls can be made to the plugins on demand. All plugins run within the same thread. All calls to the plugin are made through a JavaScript function called "pluginRequest". Because of this, we create a Function object that points to that pluginRequest function. Then we store this function object on the ScriptPlugin object along with the scope for this plugin. Whenever a request is made, we get a new context (Context.enter();), call pluginRequest (passing in the required parameters), and then exit the context. My question: is there a better way to do this? Performance has been a little dissappointing and we wonder if we shouldn't be using the Function object? Or if we should store the context permamently? Any suggestions would be more appreciated. Thanks! Michael mike@electrotank.com .