[opensource-dev] Client Plugin System Design

Dzonatas Sol dzonatas at gmail.com
Wed Mar 17 08:21:17 PDT 2010


Ricky wrote:
> So far, barring any LL concepts, we have (as far as I know so far!) 
> two designs of plugin system:
> 1: Socket-based plugins - as�suggested�by Morgaine.
> 2: D-Bus or similar existing IPC tool.
> 3: C++ Dynamically Shared Objects - my suggestion.

4. REST/HTTP

The REST based system allows for asynchronous and synchronous flow of 
communication with completely detached paths through any possible 
transport mechanism provided, yet typically HTTP is used.

REST is quite different from the usual SOAP design and implementation 
for messages being passed back and forth. Either way, this is the level 
that plugin or client-side script designer need to think about rather 
than a lower transport protocol.

Be sure to look at the patch here for minimal REST/HTTP server added to 
the viewer:
https://jira.secondlife.com/browse/SNOW-375

That easily allows any plugin or client-side script to connect to the 
viewer like any HTTP based script would do.

Currently, already started to provide resources to work with the 
inventory. My project site: http://jira.dzonux.net:8080/browse/MVC


More information about the opensource-dev mailing list