Plugin architecture

Table Of Contents

1. Discussions
   1. Survey of Client Plugins as Potential Models
   2. Security Model Issues
   3. Dynamic Updating and Loading Of Plugins
   4. Cross Platform Issues
   5. PlugIns effecting Client Stability
   6. Plugin <--> LSL Communication Channels
2. Required Changes

Required Changes

Some changes in the code will be required to support plugins.

• Complete GUI and other classes with functions that would be expected to exist, but don't because nothing needed them yet. For instance, add method overloads that should logically exist.
• Allow multiple callbacks per message, as well as unregistering a previously registered one. Currently only one callback can be registered per message type.
• Verify that all the callbacks work in such a way that they wouldn't be confused by plugins. When a callback for a reply to a request runs it must make sure that the data to arrived is what was requested, and if not, ignore it.
• Add internal callbacks for events such as rendering a frame, receiving a chat message, etc.